Uploaded image for project: 'Kogito'
  1. Kogito
  2. KOGITO-7058

[KSW][OpenAPI] - Add support for programmatic configuration of OidcClients for Oauth2

XMLWordPrintable

    • Icon: Enhancement Enhancement
    • Resolution: Won't Do
    • Icon: Minor Minor
    • None
    • None
    • Serverless Workflow Engine
    • None
    • False
    • None
    • False
    • ---
    • ---

      Today, KOGITO-6970 OAuth2 support can be configured via application properties:

      quarkus.oidc-client.petstore_auth.auth-server-url=${keycloak.url}
quarkus.oidc-client.petstore_auth.discovery-enabled=false
quarkus.oidc-client.petstore_auth.token-path=/tokens
quarkus.oidc-client.petstore_auth.credentials.secret=secret
quarkus.oidc-client.petstore_auth.grant.type=password
quarkus.oidc-client.petstore_auth.grant-options.password.username=alice
quarkus.oidc-client.petstore_auth.grant-options.password.password=alice
quarkus.oidc-client.petstore_auth.client-id=petstore-app

      Alternatively, users could programmatically create their own OidcClientConfig:

      @Path("/clients")
public class OidcClientResource {

    @Inject
    OidcClients clients;

    @GET
    public String getResponse() {
        OidcClientConfig cfg = new OidcClientConfig();
        cfg.setId("myclient");
        cfg.setAuthServerUrl("http://localhost:8081/auth/realms/quarkus/");
        cfg.setClientId("quarkus");
        cfg.getCredentials().setSecret("secret");
        Uni<OidcClient> client = clients.newClient(cfg);
        // use this client to get the token
    }
}

      The extension should also support this method of defining the configuration. See: https://quarkus.io/guides/security-openid-connect-client#use-oidcclients

              wmedvede@redhat.com Walter Medvedeo
              rhn-support-zanini Ricardo Zanini
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated:
                Resolved: