Closed Roman-Kacharaba closed 2 months ago
extraParams
should be passed to the method you're using to send a request to /authorize
, like getWithRedirect
extraParams
should be passed to the method you're using to send a request to/authorize
, likegetWithRedirect
Can we pass extraParams to config when initialiazing Okta ( like new OktaAuth(config) ) without getWithRedirect or getWithoutPrompt ?
That is not currently supported. Do mind elaborating on your use case?
That is not currently supported. Do mind elaborating on your use case?
Is there any other way to pass extraParams except getWithoutPrompt or getWithRedirect ?
Maybe we can pass some addional field to config object to avoid calling getWithoutPrompt or getWithRedirect ?
That is not supported
That is not currently supported. Do mind elaborating on your use case?
Can you add support for this use case ?
Can you elaborate on your use case? How does your app result in an /authorize
call without using a method to do so?
Describe the bug
When I'm trying to initialize Okta with extraParams: {.foo: 'bar' }, they are not visibly in /authorize call
Reproduction Steps?
When I'm trying to initialize Okta with extraParams: {.foo: 'bar' }, they are not visibly in /authorize call
const tokenParams = { clientId: oktaConfig.clientId, issuer: oktaConfig.issuer, redirectUri:
${window.location.origin}/login/callback
, pkce: true,};
const oktaAuth = new OktaAuth(tokenParams);
I'm passing const oktaAuth = new OktaAuth(tokenParams); to Security component from @okta/okta-react library like - <Security oktaAuth={oktaAuth} restoreOriginalUri={restoreOriginalUri}> {children}
SDK Versions
Version 7.9.0
Additional Information?
No response