Logon to 3scale using admin credentials not working

[chandra-potula]

Logon to 3scale using admin credentials fails:

Credentials applied from the secret system-seed as described in the readme.md. Is some thing missed ?

NOTE: FYI, I have created project 3scale-project instead 3scale.

[chandra-potula]

Also just an observation: few of the readme.md steps might have been outdated since the newer version of RH SSO and 3scale. Describing with the exact version of operators may help if they are available on the latest openshift 4.x (4.16 or newer). Thanks !

[guimou]

Hi!
Regarding the login, the credentials are effectively ADMIN_USER and ADMIN_PASSWORD items from the system-seed Secret.
However, from your screenshot, I see the URL you are trying to reach is https://maas-admin.apps.prod.rhoai..... This is an internal Red Hat demo system, so of course you won't have access. You must use the address of the cluster where you have deployed you own 3Scale. The Route will start with the same maas-admin as I put in the instructions, but the rest of the URL will be totally different.
Also, yes, there are some info missing, but this repo was not intended to be used as a full recipe to deploy/configure the solution, it was just some "enhanced notes". However, I am working on structuring all of this better to have a full up to date guide.

[chandra-potula]

@guimou thanks for the quick pointer, Now I am able to proceed further with 3scale and currently trying step : In Developer Portal->Settings->SSO Integrations, create a new SSO Integration: of type Red Hat Single Sign On.

test the authentication flow failed :

Clicked keycloak-oidc and I see below error.

Do I miss some thing here ?

Just wondering, If I look back to previous steps at https://github.com/rh-aiservices-bu/models-aas/tree/main?tab=readme-ov-file#red-hat-sso one of the step was : For the moment, set Valid Redirect URLs to *

So was it needed to be updated some point in later ?

[guimou]

No, it's not required. Although recommended to filter out which redirect to your authorizing.
You must have a configuration error somewhere else.