Tuesday, 15 May 2012

access token - On WSO2 Implicit flow failing but works for Authorization flow -


Opening I started learning OpenID Connect. This is a comprehensive learning curve. I am working with WSO 2 for months as my identity server. The identity of the theoretical has also been used with 3 servers, which is a C # based open solution, I have installed a Microsoft client in C # and it works very well with the authorization code grant ("authorization") on WSO2. Then I set the implicit code flow grant ("Implicit"). Access_token looks good again. I have removed it from the javascript page from the "hash" section. However, when I try to use it as a barerer token in the authorization header of the full request for claims, it throws the following error as a response.

Status code: 500, Regency: 'Internal server error', version: 1.1, content: system. met. Hpp Stream Content, Header:


: Accept-Encoding
Connection: Close Date: Mon, 16 Mar 2015 13:14:47 GMT
Server: WSO2 Server: Carbon Server : Server content-length: 6068 content-type: text / html; Charset = utf-8
}

It seems that access_token is incorrect from Implicit.

If I transpose a copy of access_code from the execution of an authorization execution, in the form of a string, any ideas that it works perfectly will be welcomed.
I have the authority for authorization and transplantation for both

Any ideas will be useful.


No comments:

Post a Comment