Kotlin Client SDK: Update sign-into-mobile-app-redirect guide to the 2.x SDK#6221
Open
brentschaus-okta wants to merge 4 commits into
Open
Kotlin Client SDK: Update sign-into-mobile-app-redirect guide to the 2.x SDK#6221brentschaus-okta wants to merge 4 commits into
brentschaus-okta wants to merge 4 commits into
Conversation
…x SDK Rewrite the Android code samples, config, and dependencies for the okta-mobile-kotlin 2.x SDK (BOM 2.0.3), the Kotlin twin of the Swift refresh in #5953. The guide previously targeted the 1.x SDK (CredentialBootstrap, OidcClient, OidcClientResult), which was removed or renamed in 2.x and no longer compiles. - addconfigpkg: BOM 1.0.0 -> 2.0.3; auth-foundation-bootstrap -> auth-foundation + oauth2 - configmid: discoveryUrl/DISCOVERY_URL -> issuer/ISSUER (drop .well-known/openid-configuration suffix) - opensignin: AuthFoundation.initializeAndroidContext + OidcConfiguration.default; WebAuthentication(), OAuth2ClientResult, Credential.store/setDefaultAsync/getDefaultAsync/delete; null-check default credential for sign-in state - getuserinfo, usetoken: CredentialBootstrap.defaultCredential() -> Credential.getDefaultAsync() - samplecode: point to okta-mobile-kotlin/tree/master/app - index: fix 'to user an' -> 'to use an' title typo from #5953 Verified every snippet against the okta-mobile-kotlin master sample app.
This comment was marked as outdated.
This comment was marked as outdated.
…chor Follow-on cross-link cleanup alongside the Kotlin guide update. - OCI-mobile and OCI-secure-your-first-web-app journeys: the mobile redirect bullets pointed only at the iOS guide. Repoint to the framework-neutral guide path so the updated Kotlin/Android version is also surfaced. - keep-user-signed-in related.md (android + ios): the 'Check for a session at startup' link pointed to a #check-for-a-session-at-startup anchor that no longer exists in the redirect guide. Repoint to the standalone check-for-session guide, matching how the guide now links it.
This comment was marked as outdated.
This comment was marked as outdated.
97f87ba to
7b2df23
Compare
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
This comment was marked as outdated.
Add an inline 'sdkname' StackSnippet (Okta Client SDK for Swift / for Kotlin) and use it for the generic SDK references in the shared index, so readers see their platform's SDK named in the prose. Also name the SDK explicitly in the per-framework dependency snippets. Matches the dominant 'Okta Client SDK for <lang>' phrasing already used across the docs.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description:
1. Update the Android (Kotlin) guide to the 2.x SDK
Updates the Android (Kotlin) version of the "Sign into mobile app redirect" guide to the current
okta-mobile-kotlin2.x SDK (BOM2.0.3). This is the Kotlin counterpart to the Swift refresh in #5953. The guide previously targeted the 1.x SDK (CredentialBootstrap,OidcClient,OidcClientResult), which was removed or renamed in 2.x and no longer compiles against today's SDK.1.0.0→2.0.3;auth-foundation-bootstrap→auth-foundation+oauth2(keptweb-authentication-ui).discoveryUrl/DISCOVERY_URL→issuer/ISSUERin the properties list, placeholder table, andbuildConfigFieldblock; dropped the/.well-known/openid-configurationsuffix (2.x derives this automatically).AuthFoundation.initializeAndroidContext(this)+OidcConfiguration.default; sign-in/sign-out useWebAuthentication(),OAuth2ClientResult, andCredential.store/setDefaultAsync/getDefaultAsync/delete. Sign-in state is now a null-check on the default credential (aCredentialcan no longer hold a null token in 2.x).CredentialBootstrap.defaultCredential()→Credential.getDefaultAsync().okta-mobile-kotlin/tree/master/app), mirroring the Swift PR.to user an→to use antitle typo introduced in Swift Client SDK: Update "sign in to mobile - redirect" guide #5953 (also corrects the iOS page, since the title is shared).Every code snippet was verified against the
okta-mobile-kotlin@mastersample app (SampleApplication.kt,BrowserViewModel.kt,DashboardViewModel.kt) and theCredentialsource.2. Cross-link cleanup (related to the above)
keep-user-signed-inrelated links (android + ios) pointed to a#check-for-a-session-at-startupanchor that no longer exists in the redirect guide. Repointed to the standalonecheck-for-sessionguide, matching how the redirect guide now references it.3. Inline naming StackSnippet
What's changed?
Names the platform SDK per framework in the Sign into a mobile app using the redirect model guide, so readers see their own platform's SDK named in the prose rather than a generic "Okta SDK."
Adds an inline sdkname StackSnippet that resolves to Okta Client SDK for Swift (iOS) / Okta Client SDK for Kotlin (Android).
Wires that snippet into the three generic SDK references in the shared main/index.md (Add packages, Define a callback route, Open the sign-in page).
Names the SDK explicitly in the per-framework dependency snippets (addconfigpkg.md): "Okta Mobile Kotlin library" → "Okta Client SDK for Kotlin"; "Okta OIDC package" → "Okta Client SDK for Swift package". This matches the dominant "Okta Client SDK for " phrasing already used across the docs, and mirrors the same change made to the sign-users-in-mobile-self-hosted guide.
Is this PR related to a Monolith release? No.
Resolves:
Netlify Preview Link:
Preview link