-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changing authorization to Okta #2
Comments
@ravircit sorry for the delay in replying. Are you thinking in terms of altering the console code on your side? We haven't tested yet, but you can update /assets/config.json to use "saml" instead of "cognito". Have you tried that already? |
@reganwolfrom Thanks for reply. Yes I have tried that. It just redirect to Okta with normal login flow. not handling call back. I want to completely by pass Cognito user authentication, to replace with Okta. Is that possible? |
Sorry for the delay in getting back to you, @ravircit. Right now, if Okta is not working with the current flow, there are two ways I can think of to use Okta directly:
For #2, we have a tutorial you can look at: https://docs.formkiq.com/docs/tutorials/using-a-server-side-proxy Otherwise, we can set up Okta as part of a FormKiQ Pro installation. Hope this helps. Thanks! |
Is that possible to change auth from Cognito to Octa. have done the set up Okta as a SAML identity provider in an Amazon Cognito user pool. but redirection doen't work
The text was updated successfully, but these errors were encountered: