Hello Swennergren
It still works fine for me.
https://xxxx.xxx.xxx.xx/portal/ - Common Services using keycloak - usually sysadmin/sysadmin
https://xxxx.xxx.xxx:20961/ - Administrator local end point - usually sysadmin/sysadmin
https://xxxx.xxx.xxx:20964/ - Protector local end point - usually root@master/<root password>
https://xxxx.xxx.xxx:22016/Analytics/ - Analyzer local end point usually system/manager
https://xxxx.xxx.xxx:22016/Automation/ - Automator local end point usually system/manager
https://xxxx.xxx.xxx:8443 - Detailed View or probe, username and password set when you loaded the license.
You should be able to authenticate locally but also via keycloak(and the common services). I tried finding the docs that was on knowledge but it seems like these weren't carried over to the docs site. If there's a specific product you want to authenticate to via keycloak I can see if I can find it in my own notes and post if here if that would be helpful.
------------------------------
William Jansen Van Nieuwenhuizen
Hitachi Vantara
------------------------------
Original Message:
Sent: 02-03-2025 09:07
From: Swennergren Henrik
Subject: OPS-C Administrator not directly accessable
SOLVED!!
After reboot of our entire OPS-C environment, it works fine again
Hi!
We seem to have got some issue in our OPS-C environment.
We can´t no longer log in to OPS-C Administrator directly.
https://xxx.xxx.xxx.xx:20961/#/login
We will get error message saying "Invalid username or password"
This also concerns the API access to be able to get reports out. We only get "respons 401" from the API call.
But, if we go to OPS-C Portal (https://xxxx.xxx.xxx.xx/portal/) it works fine.
And from there we can access Administrator page. (also Analyzer and Protector and all other)
We do have another instance where the same user account is used, and there all works fine.
What could be the issue that we are no longer available to access OPS-C Administrator directly?
Any ideas?
Cheers