-
Bug
-
Resolution: Done
-
Major
-
None
-
4.13
-
Quality / Stability / Reliability
-
False
-
-
None
-
None
-
No
-
None
-
None
-
Rejected
-
Hypershift Sprint 234
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description:
Bug edited as Logging in with IDP works, token generation fails - Eldar
There is a failure after creating an htpasswd token generation, after logging in to console.
Steps:
1)Create hosted cluster by ROSA CLI:
rosa create cluster --cluster-name eldh2 --sts --role-arn arn:aws:iam::425464789085:role/eldw-Installer-Role --support-role-arn arn:aws:iam::425464789085:role/eldw-Support-Role --controlplane-iam-role arn:aws:iam::425464789085:role/eldw-ControlPlane-Role --worker-iam-role arn:aws:iam::425464789085:role/eldw-Worker-Role --operator-roles-prefix eldw-label-4-q0w0 --region us-west-2 --replicas 2 --compute-machine-type m5.xlarge --machine-cidr 10.0.0.0/16 --service-cidr 172.30.0.0/16 --hosted-cp --subnet-ids subnet-0bd4e7b02a0f9ff07,subnet-0181c4dd03eb6e352 --version 4.12.0 --properties cert-manager:use
2) Create htpasswd IDP:
{"type": "HTPasswdIdentityProvider","name": "test-htpasswd-idp","htpasswd": {
"users":{ "items": [{"username": "foo","password": "Foo12345678910"}]}} }
4) When you login with the above credentials to the console, it will work and you will reach the token generation page. Click the "display token", you will get
Error getting token: Post "https://oauth.eldh2.l6j0.s3.devshift.org:443/oauth/token": socks connect tcp 127.0.0.1:8090->oauth.eldh2.l6j0.s3.devshift.org:443: unknown error host unreachable
5) Attempt to login with credentials will be successful:
[eweiss@eweiss Desktop]$ oc login https://api.eldh2.l6j0.s3.devshift.org:443 [eweiss@eweiss Desktop]$ oc login https://api.eldh2.l6j0.s3.devshift.org:443 --username foo --password Eldar123456789 Login successful.You don't have any projects. You can try to create a new project, by running oc new-project <projectname>
