[Jupiter] Handle custom security policy

[mouligno]

:rainbow: Feature

As an API Publisher, I want to use custom security policy

:sunrise_over_mountains: Additional information

• we only got Keyless, api-key, jwt or oauth2
• we can already add new security plugins
• SecurityPolicy concept still got hardcoded value for plan security
• which convention should we use to make it dynamic ?
• documentation to add its own security policy ?

See source code

private Policy buildSecurityPolicy(String security) {
    Policy secPolicy = new Policy();
    switch (security) {
        case "KEY_LESS":
        case "key_less":
            secPolicy.setName("key-less");
            break;
        case "API_KEY":
        case "api_key":
            secPolicy.setName("api-key");
            break;
        case "OAUTH2":
            secPolicy.setName("oauth2");
            break;
        case "JWT":
            secPolicy.setName("jwt");
            break;
    }
    return secPolicy;
}

:link: Dependencies

Link a story or other related things...

:camera: Mockups

Insert screenshots, drawings...

:books: Documentation required

Provide link to the issue for documentation update

:superhero: Acceptance criteria

• [ ] Given a custom security plugin Then I can use it When I call my API
• [ ] Given '...' Then '...' When '...'
• [ ] Given '...' Then '...' When '...'

:warning: Potential impacts

Which other features may be impacted by this fix. This could be populated after fix

What are the impacted versions?

:rocket:

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.