wso2is

问题 I am doing sso sample(travelocity.com) example. When I am trying to access user info with oauth access token using this command, curl -k -H "Authorization: Bearer b68ba941c9da3d2644d8a63154d28" https://localhost:9443/oauth2/userinfo?schema=openid I am getting follwing error {"error":"insufficient_scope","error_description":"Access token does not have the openid scope"} please help, thank you 回答1: When you make the first request to the authorization endpoint, you have to include openid in the

问题 I am doing sso sample(travelocity.com) example. When I am trying to access user info with oauth access token using this command, curl -k -H "Authorization: Bearer b68ba941c9da3d2644d8a63154d28" https://localhost:9443/oauth2/userinfo?schema=openid I am getting follwing error {"error":"insufficient_scope","error_description":"Access token does not have the openid scope"} please help, thank you 回答1: When you make the first request to the authorization endpoint, you have to include openid in the

问题 My username is mapped to email while creating a user with payload { "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ], "name": { "formatted": "Careerex Admin" }, "userName": "careerex.admin@in.aanasonic.com", "password": "abc!12345", "profileUrl": "www.gmail.com", "phoneNumbers": [ { "type": "mobile", "value": "9876543210" } ], "locale": "Delhi" } I am getting following error regarding restrictions of username- { "schemas": [ "urn:ietf:params:scim:api:messages:2.0:Error" ],

问题 My username is mapped to email while creating a user with payload { "schemas": [ "urn:ietf:params:scim:schemas:core:2.0:User" ], "name": { "formatted": "Careerex Admin" }, "userName": "careerex.admin@in.aanasonic.com", "password": "abc!12345", "profileUrl": "www.gmail.com", "phoneNumbers": [ { "type": "mobile", "value": "9876543210" } ], "locale": "Delhi" } I am getting following error regarding restrictions of username- { "schemas": [ "urn:ietf:params:scim:api:messages:2.0:Error" ],

问题 I am using the WSO2 Identity Server 5.10.0 and I am trying to implement WSO2IS with an external ADFS Server. I have followed https://docs.wso2.com/display/IS570/Configuring+AD+FS+as+a+Federated+Authenticator example and configure my ADFS as Identity Provider from the WSO2 Admin Console. The server is able to redirect to the ADFS login page but when the ADFS sends a callback to the WSO2IS it is throwing NullPointerException. The complete Stack trace is as follows: [2020-04-02 17:49:56,407]

问题 I am using the WSO2 Identity Server 5.10.0 and I am trying to implement WSO2IS with an external ADFS Server. I have followed https://docs.wso2.com/display/IS570/Configuring+AD+FS+as+a+Federated+Authenticator example and configure my ADFS as Identity Provider from the WSO2 Admin Console. The server is able to redirect to the ADFS login page but when the ADFS sends a callback to the WSO2IS it is throwing NullPointerException. The complete Stack trace is as follows: [2020-04-02 17:49:56,407]

问题 I am using WSO2 Identity Server in my project for authentication and authorization and in my WSO2 server primary data source is LDAP. For authorization, I need to fetch 2 things 1) How many roles assigned to the user. 2) How many users assigned to the role. So I am using getRoleListOfUser and getUserListofRole from RemoteUserStoreManagerService web service. Now the issue is one role is assigned to around 25K users. When I execute getUserListofRole I get only 2k Users as part of the response.

问题 I use WSO2is 5.7.0 with my angular 6 app, i tried make api call from my app but i have a cors error: Cross-Origin Request Blocked: The Same Origin Policy disallows reading the remote resource at I already activated the cors enabled in oauth and authenticationendpoint, i edited de WEB-INF/web.xml of both webapps with this lines: <filter> <filter-name>CORS</filter-name> <filter-class>com.thetransactioncompany.cors.CORSFilter</filter-class> <init-param> <param-name>cors.allowOrigin</param-name>

问题 I am using WSO2-IS 5.3.0. I have configured many service provider and SAML SSO is working as expected. But when it comes to Logout, One functionality is working fine. It means it redirects me to a common logout page after an invaliding session. Here, I have one case, I have one service provider for it, I need to perform single logout but it should redirect to my custom login page. Though IS providing the option to configure return URL(SLO Response URL) you can see in the below screenshot. I

问题 I have dockerized our Angular application which have been using WSO2 as API manager . After doing the configurations, i was able to run the application successfully and able to hit all existing api's. The only issue arises when i tried to use oath2/token api for performing login operation of our customer . Even though, the same code was used to perform authentication earlier(before dockerization) without any issues,now i am getting error as { "error": "invalid_grant", "error_description":