okta-api

问题 I am building a Vue.js application with Okta authentication, loosely based on the following: https://developer.okta.com/blog/2018/02/15/build-crud-app-vuejs-node and https://developer.okta.com/docs/concepts/okta-hosted-flows/. I am trying to gain a better understanding of how to use a callback route when adding Okta to the Vue router. According to these docs, after authenticating the user in the Okta sign up page, the app is briefly redirected to an unseen component called Auth.handleCallback

问题 We have the following architecture: .NET core 3.1 web application using razor pages, jQuery, etc as the UI (not an angular application) .NET core 3.1 web api application serving as our api layer Okta as our identity provider I have implemented the Okta widget and middleware in the web application. Users can login, and after that happens I’m able to get a ClaimsPrincipal, access all of their scopes, and get to any custom profile data I’ve stored via open id. I'm able to secure views through

问题 I recently built a Vue.js application with Okta authentication. I am attempting to deploy this application on Netlify. After setting up a new project in Netlify, I imported the Vue.js application into the Netlify project from GitHub. I reconfigured the router in the application so that redirect_uri in the Okta initializer reflects the new Netlify URL: import Auth from "@okta/okta-vue"; Vue.use(Auth, { issuer: "https://xxx-xxxxxx.okta.com/oauth2/default", client_id: "xxxxxxxxxxxxxxxxxxxx",

问题 I recently built a Vue.js application with Okta authentication. I am attempting to deploy this application on Netlify. After setting up a new project in Netlify, I imported the Vue.js application into the Netlify project from GitHub. I reconfigured the router in the application so that redirect_uri in the Okta initializer reflects the new Netlify URL: import Auth from "@okta/okta-vue"; Vue.use(Auth, { issuer: "https://xxx-xxxxxx.okta.com/oauth2/default", client_id: "xxxxxxxxxxxxxxxxxxxx",

问题 I'm using Okta for user authentication of my SPA (+ Express backend). How can I use the Okta API to show/hide content based on group membership? e.g. if I want to show some menu items if the active user is a member of a specific group. Is there anything in the Okta React SDK? I'm coming up short, product seems great, docs seems less so. I've found this API https://developer.okta.com/docs/api/resources/users.html#get-member-groups I'm however unsure of how to best use this from my app. when

问题 I'm trying to integrate with Okta SSO by implementing SAML 2.0 in my website as Service Provider (SP) and Okta env. as my Identity Provider (IDP) I can't understand how to configure my IDP to return for each Auth request, the groups a user is in. How can it be done? Also, Is it possible to have service account in my IDP that my backend can ask the IDP directly if a user is inside some specific group? 回答1: It is possible to add groups to the SAMLResponse by configuring the SP App in the Okta

问题 I have followed the guide https://ultimatesecurity.pro/post/okta-saml/ , to configure OKTA Saml with keycloak. After this configuration, I see Okta/saml login button on login page, clicking on which, the user is redirected to Okta login/SSO. Now, is there a way to avoid clicking on this button everytime such that when the keycloak login page appears, user is auto redirected to Okta SSO automatically instead of shown keycloak login form with okta redirect button? If not, is it possible to

问题 We have a spa (Angular 2) that we are trying to integrate with okta. I created an app in okta with SWA sign on method. I click on the app and it redirects me to my spa app as expected. However, I do not see and information being passed on the redirect. How do I validate that the login was successful? Is there some token info that I can validate? Something else? Thanks! 回答1: The SWA sign on method depends on the Okta plugin - do you have it installed? If so, when you hit your login page (and

问题 I am using the okta oAuth to do the authentication and authorization with angular 8 application. Since getting the 'https://dev-166545.okta.com/oauth2/aus1igd7yewoAs4xa357/.well-known/openid-configuration is causing the issue I have added the redirect URL in the okta trusted origin. I can't add the URLs in the CORS because of company policy. How can I solve the issue CORS Access to XMLHttpRequest at 'https://dev-166545.okta.com/oauth2/aus1igd7yewoAs4xa357/.well-known/openid-configuration'

问题 We are developing an application in which we plan to use Okta as the ID provider. However, this application will be hosted in Azure and we would like to use the Azure ACS for Federation. However, off late we came to know that ACS is going be integrated with Azure AD (http://blogs.technet.com/b/ad/archive/2015/02/12/the-future-of-azure-acs-is-azure-active-directory.aspx). I am bit confused here. I understand AD provides the directory services and will be used for authentication. In our case,