Replaces instances of himself
with more inclusive language
Closes #12300
This commit is contained in:
parent
f9c6ea84ad
commit
91e88f554e
4 changed files with 5 additions and 5 deletions
|
@ -75,7 +75,7 @@ with password `secret` .
|
|||
|
||||
Then in your web browser open `http://localhost:8080/kerberos-portal` . You should be logged-in automatically through SPNEGO without displaying Keycloak login screen.
|
||||
Keycloak will also transmit the delegated GSS credential to the application inside access token and application will be able to login with this credential
|
||||
to the LDAP server and retrieve some data from it (Actually it just retrieve few simple data about authenticated user himself).
|
||||
to the LDAP server and retrieve some data from it (Actually it just retrieve few simple data about authenticated user themself).
|
||||
|
||||
|
||||
Troubleshooting
|
||||
|
|
|
@ -75,7 +75,7 @@ public class MSADUserAccountControlStorageMapper extends AbstractLDAPStorageMapp
|
|||
|
||||
@Override
|
||||
public LDAPOperationDecorator beforePasswordUpdate(UserModel user, LDAPObject ldapUser, UserCredentialModel password) {
|
||||
// Not apply policies if password is reset by admin (not by user himself)
|
||||
// Not apply policies if password is reset by admin (not by user themself)
|
||||
if (password.isAdminRequest()) {
|
||||
return null;
|
||||
}
|
||||
|
|
|
@ -907,7 +907,7 @@ action=Aktion
|
|||
#client-scopes.evaluate.granted-realm-effective-roles.tooltip=Client has scope mappings for these roles. Those roles will be in the access token issued to this client if authenticated user is member of them
|
||||
#client-scopes.evaluate.granted-client-effective-roles=Granted Effective Client Roles
|
||||
#generated-access-token=Generated Access Token
|
||||
#generated-access-token.tooltip=See the example token, which will be generated and sent to the client when selected user is authenticated. You can see claims and roles, which the token will contain based on the effective protocol mappers and role scope mappings and also based on the claims/roles assigned to user himself
|
||||
#generated-access-token.tooltip=See the example token, which will be generated and sent to the client when selected user is authenticated. You can see claims and roles, which the token will contain based on the effective protocol mappers and role scope mappings and also based on the claims/roles assigned to user themself
|
||||
|
||||
manage=Verwalten
|
||||
authentication=Authentifizierung
|
||||
|
|
|
@ -1156,9 +1156,9 @@ client-scopes.evaluate.granted-realm-effective-roles=Granted Effective Realm Rol
|
|||
client-scopes.evaluate.granted-realm-effective-roles.tooltip=Client has scope mappings for these roles. Those roles will be in the access token issued to this client if the authenticated user is a member of them
|
||||
client-scopes.evaluate.granted-client-effective-roles=Granted Effective Client Roles
|
||||
generated-access-token=Generated Access Token
|
||||
generated-access-token.tooltip=See the example access token, which will be generated and sent to the client when selected user is authenticated. You can see claims and roles that the token will contain based on the effective protocol mappers and role scope mappings and also based on the claims/roles assigned to user himself
|
||||
generated-access-token.tooltip=See the example access token, which will be generated and sent to the client when selected user is authenticated. You can see claims and roles that the token will contain based on the effective protocol mappers and role scope mappings and also based on the claims/roles assigned to user themselves
|
||||
generated-id-token=Generated ID Token
|
||||
generated-id-token.tooltip=See the example ID Token, which will be generated and sent to the client when selected user is authenticated. You can see claims and roles that the token will contain based on the effective protocol mappers and role scope mappings and also based on the claims/roles assigned to user himself
|
||||
generated-id-token.tooltip=See the example ID Token, which will be generated and sent to the client when selected user is authenticated. You can see claims and roles that the token will contain based on the effective protocol mappers and role scope mappings and also based on the claims/roles assigned to user themselves
|
||||
generated-user-info=Generated User Info
|
||||
generated-user-info.tooltip=See the example User Info, which will be provided by the User Info Endpoint
|
||||
|
||||
|
|
Loading…
Reference in a new issue