-
Notifications
You must be signed in to change notification settings - Fork 23
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
* Move to PHP v8.1 * Move to psalm level 1 * Remove dependency on steverhoades/oauth2-openid-connect-server * Move ClaimTranslatorExtractor to Utils * Move ConfigurationService to src * Rename ConfigurationService to ModuleConfig * Move to module config constants * Normalize codebase * First Symfony route (OP configuration) * Update tests * Set SSP requirement to 2.1 * Update upgrade log --------- Co-authored-by: Marko Ivančić <[email protected]>
- Loading branch information
Showing
265 changed files
with
4,971 additions
and
4,066 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file was deleted.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,12 +1,12 @@ | ||
# Set JSON type for claims | ||
|
||
You can set the type of claim by prefixing the name with `int:`, `bool:` or `string:`. If no prefix is set then `string` | ||
is assumed. In the rare event that your custom claim name starts with a prefix (example: `int:mycustomclaim`) you can add an one of | ||
the type prefixes (example: `string:int:mycustomclaim`) to force the module to release a claim with the original prefix in it | ||
(example: claim `int:mycustomclaim` of type `string`) | ||
is assumed. In the rare event that your custom claim name starts with a prefix (example: `int:mycustomclaim`) you can | ||
add one of the type prefixes (example: `string:int:mycustomclaim`) to force the module to release a claim with the | ||
original prefix in it (example: claim `int:mycustomclaim` of type `string`) | ||
|
||
# Release photo | ||
|
||
The OIDC `picture` claim is a url, while the `jpegPhoto` ldap attribute is often a b64 string. To use `jpegPhoto` you can | ||
try using an authproc filter to turn it into a data url by adding `data:image/jpeg;base64,` prefix. The support for data urls | ||
amongst OIDC client is unknown. | ||
The OIDC `picture` claim is an URL, while the `jpegPhoto` LDAP attribute is often a b64 string. To use `jpegPhoto` you | ||
can try using an authproc filter to turn it into a data url by adding `data:image/jpeg;base64,` prefix. The support | ||
for data URLs amongst OIDC client is unknown. |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.