Skip to content
This repository was archived by the owner on Nov 24, 2022. It is now read-only.

Conversation

@aronszabo
Copy link
Member

No description provided.

lindyblackburn and others added 30 commits February 23, 2020 02:27
Keycloak 10 returns the error "invalid_scope" when a client tries to
get an access token with no scopes.

Fix it.

Signed-off-by: Naoto Kobayashi <[email protected]>
correct check for duplicate email
using composer for the oauth lib dependency, autoloading for our own
classes. Services are now their own action plugins to inherit from our
Service class.

All still untested and broken
somewhat works already
This manually applies daviddesberg/PHPoAuthLib#567 once it has been
merged, a proper composer checkout should be used again
we want to force backend implementors to think about scopes
flag indicating that login is in progress was not cleared from session
Add Keycloak scope to support Keycloak 10
The new OAuthManager is now the main flow manager and should make it
easier to follow the flow. The Session class encapsulates all session
and cookie accesses. A new guid paradigma should make invisible relogins
possible when the session expired. Needs all major cleanup but a first
login worked.
Gilson Caldeira and others added 30 commits March 29, 2023 19:00
This is to exclude unrelated files for installation
Although http status code and http error message are helpful in error handling,
TokenResponseException, throwed by oauth\HTTPClient if an error occured during
the http request, does not have fields/methods which indicate them directly.

Solve it by adding HttpTokenResponseException which has indicators of http status
code and http error message, and throwing it instead of TokenResponseException.

Signed-off-by: Naoto Kobayashi <[email protected]>
Add HttpTokenResponseException making error handling easy
Because response body is also helpful for error handler.

Signed-off-by: Naoto Kobayashi <[email protected]>
Add http response body to HttpTokenResponseException
logoff is called a lot when a user is not authenticated yet. This can
interfere with the oauth login process when calls are made while the
user is at the IdP, for example triggered by AJAX beacons like created
by the statistics plugin.
There is no real reason to delete the temporary session data. We can
simply keep it until it is used or replaced by new data.
The login cookie might not be set by oauth. That's fine but we need to
avoid the warnings.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.