AADS 8.1.3 Keycloak and Utility Server GUI

[wallot]

Folks,

I've installed a pair of AADS 8.1.3.

I've enabled keycloak and OAuth/OAth2. Also have enabled utility server.

I can access the AADS GUI using

https://<

AADS IP Address or FQDN > :8445/admin on both without issue.

I'm trying

https://<

US IP Address >:1543/admin.html for utility and get Forbidden (You don't have permission....).

https://<

US IP Address > gets the RHEL Test page. The port is what is shown when configuring US VIP.

I'm trying

https://<

AADS IP Address>:9081/auth/admin for the keycloak admin.

There appears to be default ports assigned yet the admin guide does not denote these default ports.

Any ideas out there? BTW, the AADS are replicated to SMGR.

Thanks!

 

[dclark1111]

For the Utility server admin I use -

https://SERVER:8543/cgi-bin/common/login/webLogin

- Can you see if that lets you in the Utility server side. I can login with the admin username and password set during the install.

Hope that helps. I am fighting with AADS right now as well - Good Luck!

 

[wallot]

Thanks dclark111

I get not found on 8543 and forbidden on 1543

 

[Sean655]

This isn't anything I know much about but I believe the utility server no longer has a web interface in version 8.

 

[kyle555]

Your url for keycloak is right, it's just on port 443

 

[wallot]

OK, I got it all figured out.

Primarily, the individual AADS FQDN shows by default at the top of the System Manager section, the FQDN needs to be changed to the cluster FQDN on each node. I kept overlooking this needed change assuming that it was correct by default.
On AADS 8.1.4:

AADS is

https://IP

address:8445/admin using cluster IP

keycloak is

https://IP

address:8443/auth/admin using cluster IP

utility server

https://IP

address:8543/admin.html

US cluster virtual

http://IP

address/filename (http must be specifically enabled on the CLI - see deploy and admin guides for commands)

https://IP

address/filename

Utility servers must be managed individually, meaning, if you make a change in one US, you need to make the same change in all other USs in that particular cluster. IP phone backups will only write to the seed node according to the docs.