okta

okta - asp.net - How do I get the User Name / Log In Id / Unique Identifier of the current user sign in? - Standard Way?

懵懂的女人 提交于 2019-12-11 04:19:32
问题 Using okta, how do I get the User Name / Log In Id / Unique Identifier of the current user signed in? I am currently working on an ASP.Net Web Forms App. After the user successfully signs in, I can get the name of the user with the code below. var name = User.Identity.Name; However, I want the Log In Id / Unique Identifier of the User. Looking at the Profile form on the okta web site, it looks like okta calls that field User Name. After doing some research, I did write up some code that gets

Okta SignIn Widget with SAML

五迷三道 提交于 2019-12-10 19:59:00
问题 We have a Single Web Page application developed with Spring Boot + AngularJS, and we want integrate Okta for the authentication part. I have created a developer account on the Okta website, and configured an application using SAML 2.0 Then I integrated the Okta Sign-in widget in an html page like this http://developer.okta.com/code/javascript/okta_sign-in_widget.html But I don’t know how to make the link between the sign-in widget and the idp saml metadata (https://dev-xxx.oktapreview.com/app

Okta Authentication Django

断了今生、忘了曾经 提交于 2019-12-10 10:21:47
问题 I have a Django app that I am trying to add Okta authentication. I currently have created a custom backend that utilizes the Okta API to authenticate a user: class OKTABackend(ModelBackend): def __init__(self, *args, **kwargs): super().__init__(*args, **kwargs) def authenticate(self, username=None, password=None): headers = { 'Authorization': 'SSWS {}'.format(<my OKTA API token>), 'Accept': 'application/json', 'Content-type': 'application/json' } authentication_payload = { 'username':

How does Single-logout works with OKTA(IDP)-Shibboleth(SP)-App

て烟熏妆下的殇ゞ 提交于 2019-12-08 10:48:53
问题 OKTA-Shibboleth(Apache)-Nakisa(Tomcat) SSO is working for logging-in. Now, I need to configure Logout. So, user logs out from the app, user needs to be redirected to OKTA page with tiles. But, currently,user is redirected to the app again. It's sending user to /logout?redirect=default.html but that default.html is captured by Apache rule and logging user back in. It looks like it needs to hit https://xxxx/Shibboleth.sso/Logout. When I access this url, it says logout is successfully done

OKTA integration issue with Shibboleth SP

安稳与你 提交于 2019-12-08 07:33:50
问题 I am doing a POC where I need to integrate the Shibboleth SP with OKTA idp provider.I have completed all below steps documented on OKTA official site for this integration. Install Shibboleth Service Provider 2.Configure the webserver to use Shibboleth 3.Configure Shibboleth to protect a specific folder Create an Okta SAML 2.0 Template application 4.Modify Shibboleth to use the metadata obtained from the Okta application 5.Modify the attribute-map.xml file within Shibboleth to set the

okta Angular 7 App returning a CORS error

Deadly 提交于 2019-12-08 05:11:30
问题 I am currently working through this demo: https://developer.okta.com/blog/2018/12/04/angular-7-oidc-oauth2-pkce I am setting up the OIDC Version I am getting the following error: Access to XMLHttpRequest at ‘https://dev-979343.oktapreview.com/oauth2/default/.well-known/openid-configuration’ from origin ‘http://localhost:4200’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. I have been playing around with this off and on for the

Okta sessions/me returning 404 when called from Javascript (Redux)

与世无争的帅哥 提交于 2019-12-08 02:14:34
问题 I am trying to get the current session Object from Okta using the sessions/me endpoint called from Javascript (Redux action), but I get a not found response, even when I have an active session. It's not CORS related, I enabled CORS for my domain. The best I can tell is a cookie related issue. When I call sessions/me from the browser directly, I see the browser attaching multiple cookies to my request. When I call from javascript, there are no cookies attached to the request. Is there a way,

Propagate SAML Assertion Response/Security Context to downstream Services/Apps

时间秒杀一切 提交于 2019-12-07 13:46:34
问题 We have multiple services in our environment. There are scenarios where we want the user to auto-login/silently login to one or more participating services without being challenged by the Identity Provider for credentials or communicating with the Identity Provider after the first successful login from one service. For Eg, we have a front-end UI App which we want to be authenticated using Spring Security SAML. And when the UI App communicates to back-end services we want the security context

okta Angular 7 App returning a CORS error

允我心安 提交于 2019-12-07 06:56:28
I am currently working through this demo: https://developer.okta.com/blog/2018/12/04/angular-7-oidc-oauth2-pkce I am setting up the OIDC Version I am getting the following error: Access to XMLHttpRequest at ‘ https://dev-979343.oktapreview.com/oauth2/default/.well-known/openid-configuration ’ from origin ‘ http://localhost:4200 ’ has been blocked by CORS policy: No ‘Access-Control-Allow-Origin’ header is present on the requested resource. I have been playing around with this off and on for the last 3 days and I can't seem to get it to work. I am using Angular version 7.1 (Just like the demo)

Okta Group Attributes

两盒软妹~` 提交于 2019-12-06 14:23:05
问题 I have two service providers that I am connecting to Okta in order to manage identities externally. Can you think of a way to configure Okta to accomplish the following: Associate attributes with groups, rather than directly to users. Users within groups would then inherit these attributes. Associate groups with applications, rather than directly associating users with applications. My end goal is to be able to leverage Okta for managing a role store for each service provider. I would expect