All ResourceOwners are collected automatically. #1872
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
According to #1871 another one commit that needs courage to be merged :)
ResourceOwner oauth types in
Configuration
are calculated automatically by scandir. All classes extended fromGenericOAuth[X]ResourceOwner
getoauth[X]
type. if class only implements ResourceOwnerInterface then its oauth type isunknown
.ResourceOwner key (parameter
type
in configs) should have definedResourceOwner::TYPE
constant. If constant not defined or isnull
, then key will be calculated by converting its class name withoutResourceOwner
suffix to snake_case. if neither is felt, thenInvalidArgumentException
will be thrown. Here is possible BC.Each user defined custom ResourceOwner class that implemented
ResourceOwnerInterface
will be registered automatically. Ifautoconfigure
option is disabled user have to add the taghwi_oauth.custom_resource_owner
hwi_oauth.resource_owner
to the service definition.Created final classes
OAuth1ResourceOwner
andOAuth2ResourceOwner
.Fixes #1870