Good Morning,

It seems the proper ports are open, does your java console launch  and the failure is using SSO?

can you log in with a local account?

Hi Urosa,
 

What seems to be working :

-The full name of the CommServe is properly found when entering the short name at first

-The jar files are locally copied in my profile on  the jump server as usual (I’m using a usual Java from Oracle).

But :

-I’m being prompted for the credentials as a blank window / My windows credentials are not found for SSO.

-When manually filling the fields wether with my AD credentials or a local Commvault account, this ends up with an error : ‘Unable to connect to CommCell <MyCSFullName>’.

Good Morning,

Could you try going to https://CommCell/Console which should trigger the java and have the CommCell FullName filled. 

If that works, it might required some more details on the local console install.

Hi again @Urosa ,

Thanks for your feedback.

Accessing https://CommCell/Console is working alright.

The CommCell full name is properly found when prompting the credential window.
I may have been unclear, but the blank fields are only concerning the credientials which should have been found with SSO activated (account name via AD and password).

In short, two thing don’t look right for now. The SSO,ko is one of them, but I’m more concerned about the fact that the console can’t be opened at all.
Of course, those two can be linked as there is obviously something not working properly for now.

Hi @KeyboardUser ,

Could you please open a TR with support as this may required further investigation for the SSO.

Regards,

Agreed.  Once created, please share the case number here.

Hi everyone,
Thanks for your answers.
I will share the case number when done.

Hello,

I finally found what’s been preventing the console to open on those jump servers.

I have been focusing on opening network access between those servers and it seems I got that part right after all.

Those jump servers are very remote and not using standard vlans on this infrastructure for various reasons.

This means that the standard inputs is using a vlan those jumps can’t access.The login fields have to be adjusted consequently. This is why I had to modify manually the CommServe name to an FQDN specific name using the right network path.

And without common CommCell name in the fields, no SSO retrieved.

I hope the way I’m explaining this makes sense for you.

Thank you for your help on this.

Appreciate the solid reply, @KeyboardUser !  Hopefully this helps future members