The users you are trying to log in as are likely already mapped to identities from another identity provider. You can see whether that's the case by doing `oc describe user your-username`. If so, the "claim" mappingMethod will refuse to map the htpasswd identity to the user.
If you want the htpasswd identities to automatically map to the correspondingly named user even if that user already has an associated identity, set mappingMethod to "add" On May 25, 2016, at 11:39 AM, Candide Kemmler <candide@intrinsic.world> wrote: I'm trying to configure htpasswd-based authentication but getting: "Could not create user." error my configuration is as follows: oauthConfig: assetPublicURL: https://paas.intrinsic.world:8443/console/ grantConfig: method: auto identityProviders: - challenge: true login: true mappingMethod: claim name: my_htpasswd_provider provider: apiVersion: v1 kind: HTPasswdPasswordIdentityProvider file: /etc/origin/master/users.htpasswd masterCA: ca.crt masterPublicURL: https://paas.intrinsic.world:8443 masterURL: https://paas.intrinsic.world:8443 sessionConfig: sessionMaxAgeSeconds: 3600 sessionName: ssn sessionSecretsFile: /etc/origin/master/session-secrets.yaml tokenConfig: accessTokenMaxAgeSeconds: 86400 authorizeTokenMaxAgeSeconds: 500 _______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
_______________________________________________ users mailing list users@lists.openshift.redhat.com http://lists.openshift.redhat.com/openshiftmm/listinfo/users
