You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The interface ClaimSetInterface defines a getClaims(): array method without defining the expected type for the array.
This interface is used in 2 places:
the ClaimSetEntity class implements it (alongside a confusing ScopeInterface which is not about representing a scope but a class with a getScope method) and seems to expect list<string> as the type of the array based on the usages in ClaimExtractor
the IdentityProviderInterface is expected to return a UserEntityInterface implementing it. The IdTokenResponse then expects getClaims to return array<string, string> based on the usage in the second argument of ClaimExtractorInterface
I think we should have 2 different interfaces there, one representing the claims available as a user (being a map from claim names to claim values) and another one representing a set of claim names associated with a scope.
The text was updated successfully, but these errors were encountered:
The interface ClaimSetInterface defines a
getClaims(): array
method without defining the expected type for the array.This interface is used in 2 places:
ClaimSetEntity
class implements it (alongside a confusingScopeInterface
which is not about representing a scope but a class with agetScope
method) and seems to expectlist<string>
as the type of the array based on the usages in ClaimExtractorIdentityProviderInterface
is expected to return aUserEntityInterface
implementing it. The IdTokenResponse then expectsgetClaims
to returnarray<string, string>
based on the usage in the second argument ofClaimExtractorInterface
I think we should have 2 different interfaces there, one representing the claims available as a user (being a map from claim names to claim values) and another one representing a set of claim names associated with a scope.
The text was updated successfully, but these errors were encountered: