Change Details

As noticed with @mmodell when he tried to T220653. it wouldn't let him use both "20after4" and "twentyafterfour" as a username for auth over http. This is because his shell name and cn name are different. E.g uid: twentyafterfour cn: 20after4 To use auth over http, you must use a username, @mmodell username in gerrit is twentyafterfour, so when he tried using it, it was failing to find him in ldap as it was using the cn field to search. We should find a way to allow users who have a different shell name to the cn field, to be able to auth.

As noticed with @mmodell when he tried to T220653. it wouldn't let him use both "20after4" and "twentyafterfour" as a username for auth over http. This is because his shell name ({nav uid}) and {nav cn} name are different in LDAP: | LDAP Field | Gerrit schema | Value |--|--|-- | {nav uid} | username | twentyafterfour | {nav cn} | gerrit | 20after4 To use authentication over HTTP, you must use a username, @mmodell username in Gerrit is `twentyafterfour`, so when he tried using it, it was failing to find him in LDAP as it was using the {nav cn} field to search. We should find a way to allow users who have a different shell name to the {nav cn} field, to be able to authenticate.

As noticed with @mmodell when he tried to T220653. it wouldn't let him use both "20after4" and "twentyafterfour" as a username for auth over http. This is because his shell name and cn({nav uid}) and {nav cn} name are different. in LDAP: E.g uid: twentyafterfour| LDAP Field | Gerrit schema | Value |--|--|-- cn:| {nav uid} | username | twentyafterfour | {nav cn} | gerrit | 20after4 To use authentication over httpHTTP, you must use a username, @mmodell username in gGerrit is `twentyafterfour`, so when he tried using it, it was failing to find him in ldapLDAP as it was using the cn{nav cn} field to search. We should find a way to allow users who have a different shell name to the cn{nav cn} field, to be able to auth.enticate.