Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify Auth header requirements #68

Merged
merged 1 commit into from Mar 19, 2022
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/sso/web_based_sso_flow.md
Expand Up @@ -37,10 +37,10 @@ Here is the OAuth 2.0 flow your web based application should be implementing:

grant_type=authorization_code&code=<authorization code from callback URL>

* Create a URL safe Base64 encoded string where the contents before encoding are your application's client ID, followed by a `:`, followed by your application's secret key (e.g. `URL safe Base64(<client_id>:<secret_key>)`).
* Create a Base64 encoded string, including padding, where the contents before encoding are your application's client ID, followed by a `:`, followed by your application's secret key (e.g. `Base64(<client_id>:<secret_key>)`). For example, given the input `CLIENT_ID:CLIENT_SECRET`, the resulting string should be `Q0xJRU5UX0lEOkNMSUVOVF9TRUNSRVQ=`.

* You will need to send the following HTTP headers (replace anything between `<>`, including `<>`):
* `Authorization: Basic <URL safe Base64 encoded credentials>`
* `Authorization: Basic <Base64 encoded credentials>`
* `Content-Type: application/x-www-form-urlencoded`
* `Host: login.eveonline.com`

Expand Down