The users that were generated from the GUI have disappeared. Groups are not visible either.
Cybersecurity
DevOps Cloud
IT Operations Cloud
If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more
The users that were generated from the GUI have disappeared. Groups are not visible either.
Were those users created in 11.01 or have they disappeared after an upgrade? Have they been created recently? Are you really sure the "Finish" button has been clicked to update the user database? What do you see with "omniusers -list"?
OK, that's a different story. Let's check this step by step. The first step has been:
omnicc -secure_comm -regenerate_cert xxxxxx
So I understand this was run on the cell server and xxxxxx was the name of another server. Is this indeed what was done? Please confirm.
OK, that's a different story. Let's check this step by step. The first step has been:
omnicc -secure_comm -regenerate_cert xxxxxx
So I understand this was run on the cell server and xxxxxx was the name of another server. Is this indeed what was done? Please confirm.
yes correct-
In that case I would rerun it with the name of the cell server:
omnicc -secure_comm -regenerate_cert <CS_FQDN>
This will generate the correct localhost certificate on the cell server again. Next you will need to run:
omnicc -secure_comm -reconfigure_peer <CS_FQDN>
on all clients. Please let us know the status after that.
I never tested such a configuration and it is against the DP documentation and an unsupported setup. That's all I can say. If you want to keep on running like this then feel free. But I'm assuming you may run into more issues.
Back to your user issue, you may want to run the omniusers command in debug mode and provide the debugs to support.
I was curious enough to test your strange secure_comm situation and it looks like basic functionality is still working, including the users setup. What else may have happened? What other commands may have been run to ruin the user setup?
If you have a chance to elevate a support case I would recommend that. This may need a deeper investigation.