This Question is Possibly Answered
1 "correct" answer available (10 pts) 2 "helpful" answers available (6 pts)
7 Replies
Last post:
Nov 13, 2009 3:10 AM by
Smoggy
Hi Craig
Each time you open a new VI/vSphere client session you will always (on the first navigation to the SRM UI) be challenged for the username/password for your SRM user account as SRM does not assume this is the same user account you have used to login to vCenter, it could in many cases be different.
Once you have logged in then for the duration of that VI/vSphere client session you can move around the vCenter framework as much as you like and you won't have to re-enter the details again unless you either logout of the client or someone restarted the SRM server underneath you
If you are talking about something else...like constantly having to accepted the certificate warning then let me know...you should be able to get rid of that buy simply accepting/installing the unsigned default certificate into your local windows certificate store.
cheers
Lee
Each time you open a new VI/vSphere client session you will always (on the first navigation to the SRM UI) be challenged for the username/password for your SRM user account as SRM does not assume this is the same user account you have used to login to vCenter, it could in many cases be different.
Once you have logged in then for the duration of that VI/vSphere client session you can move around the vCenter framework as much as you like and you won't have to re-enter the details again unless you either logout of the client or someone restarted the SRM server underneath you
If you are talking about something else...like constantly having to accepted the certificate warning then let me know...you should be able to get rid of that buy simply accepting/installing the unsigned default certificate into your local windows certificate store.
cheers
Lee
????
well you've still not shown exactly what is appearing that you think shouldn't be, where's the screenshot?
also if you can cut n paste the section of the admin guide along with the screenshot then it might all make sense.
at the moment your problem description isn't complete.
I want to help you but you need to help me understand what your problem description means. at the moment its not clear.
attached is a screenshot of me logging into one of my lab setups....i would expect to go through this process everytime i login at the start of each day if its a new client session. Note I am using a shared site setup so you won't see the first pop-up that lists the available sites.....
you will see the last login box regardless of whether you use credentials or ceritifcate based authentication the reason for this is that when you login to SRM you provide user level credentials which are used in conjunction with our permissions model to determine what you can/cannot do. There is an administrative session which SRM uses for server to server communication, but cannot be used for user level operations. If it was, there would be no way to limit access for specific users.
cheers
Lee
well you've still not shown exactly what is appearing that you think shouldn't be, where's the screenshot?
also if you can cut n paste the section of the admin guide along with the screenshot then it might all make sense.
at the moment your problem description isn't complete.
I want to help you but you need to help me understand what your problem description means. at the moment its not clear.
attached is a screenshot of me logging into one of my lab setups....i would expect to go through this process everytime i login at the start of each day if its a new client session. Note I am using a shared site setup so you won't see the first pop-up that lists the available sites.....
you will see the last login box regardless of whether you use credentials or ceritifcate based authentication the reason for this is that when you login to SRM you provide user level credentials which are used in conjunction with our permissions model to determine what you can/cannot do. There is an administrative session which SRM uses for server to server communication, but cannot be used for user level operations. If it was, there would be no way to limit access for specific users.
cheers
Lee
I have attached the screen shots which matches what you say is the login screen. I understand what you are saying now. The pairing is created and kept but you need to login so permissions applied per user can work. Based on what was in the SRM admin guide I thought the initial login to the VI Client would also carry in your credentials to SRM to avoid a double login.
Craig
Craig
