I’m currently evaluating the okta-mobile-kotlin
library for use in an Android application. We are considering using a third-party identity provider (IdP) such as SecureAuth, rather than Okta’s own services.
The documentation and examples primarily focus on Okta as the IdP. I would like to clarify whether okta-mobile-kotlin
is designed to be exclusively used with Okta, or if it can be configured to work with other OpenID Connect (OIDC) compliant providers like SecureAuth.
Specifically, I’d like to know:
- Is the library inherently tied to Okta-specific endpoints or features?
- Are there any configuration options or customizations that allow for the use of a different OIDC provider?
- If third-party providers are supported, are there any known limitations or considerations I should be aware of?
- If third party providers are supported, are there any examples or documentation that can be provided on how to configure the library to work with them?
Expected Behavior:
Ideally, the library would allow for configuration to point to a different OIDC provider’s endpoints (e.g., authorization, token, userinfo).
Actual Behavior:
The current documentation and examples focus solely on Okta.