okta

问题 I am currently going through this post to integrate okta into a Blazor Server Side App https://developer.okta.com/blog/2019/10/16/csharp-blazor-authentication I am currently getting “Sorry, there's nothing at this address”. I was hoping someone could provide a suggestion to my problem. Or does anyone know of an example to integrate okta into a Blazor Server Side App? Please let me know. Any help would be appreciated. I am totally spinning my wheels. Here are my okta General Settings: Below is

问题 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 have a 3rd party module that I am using for authentication- OktaAuthModule. For it to be imported in my root module (app.module.ts), it needs to first be configured like this- const config = { url: https://myurl.com/ } @NgModule({ declarations: [ ... ], imports: [ OktaAuthModule.initAuth(config), ], ... }); I need to produce a single build that can be deployed to multiple runtimes, each having a different config for this module. Using the built-in "ng build --env " works fine, but requires

问题 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 am new to react and am using okta react login. function onAuthRequired({ history }) { history.push("/login"); } function SecureApp() { return ( <Security issuer="issuer name" client_id="client id name" redirect_uri={window.location.origin + "/callback"} onAuthRequired={onAuthRequired} > <div className="App"> <SecureRoute path="/" exact={true} component={Dashboard} /> <SecureRoute path="/logout" exact={true} component={Login} /> <Route path="/login" render={() => <Login baseUrl={api.baseurl}

问题 After a successful SAML authentication : AuthNRequest;SUCCESS;0:0:0:0:0:0:0:1;https://localhost:8443/saml/metadata;http://www.okta.com/exkdwf3hodKFkefLO0h7;;; The browser is redirected back into an endless loop. I've sat with a debugger stepping through Spring code and looks like it is erroring out in BasicAuthenticationFilter calling SAMLAuthenticationProvider which doesn't support UsernamePasswordAuthenticationToken and throws an exception which in turn sends the browser into an endless

问题 I'm trying to implement the JWT Bearer Authentication in my AspNetCore MVC app (Web API only) using the JwtBearerMiddleware but am getting a 401 response with header: WWW-Authenticate: Bearer error="invalid_token", error_description="The signature key was not found" The relevant code in Startup.cs looks like this: app.UseJwtBearerAuthentication(new JwtBearerOptions { Authority = "https://example.okta.com", Audience = "myClientId" }); With the Authority URL I'd expect the middleware to query

问题 Is their any way to configure discovery document from local host before the login using OIDC-Client in angular 8 application. I have this manager which is a helper call for the OIDC client export class AuthenticationService { @Output() initialized: boolean = false; static USER_LOADED_EVENT = "USER_LOADED"; static USER_UNLOADED_EVENT = "USER_UNLOADED"; //static USER_SIGNED_OUT_EVENT = "USER_SIGNED_OUT"; //static USER_EXPIRED_EVENT = "USER_EXPIRED"; static USER_RESET_EVENT = "USER_RESET";