-
Notifications
You must be signed in to change notification settings - Fork 919
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[FR] Requesting SSO user/group modification feature (on par with govc's) #2852
Comments
Howdy 🖐 dbuenoparedes ! Thank you for your interest in this project. We value your feedback and will respond soon. If you want to contribute to this project, please make yourself familiar with the |
This issue is stale because it has been open for 90 days with no |
The ssoadmin endpoint is now used for authentication for both SOAP and REST endpoints. Previous behavior is retained: - By default, any non-empty username + password is authenticated - If vcsim '-username' and '-password' flags are given, only those credentials can be used for authentication Additional users can be added via the ssoadmin APIs or using govc for example: % govc sso.user.create -p password govc Closes vmware#2852
The ssoadmin endpoint is now used for authentication for both SOAP and REST endpoints. Previous behavior is retained: - By default, any non-empty username + password is authenticated - If vcsim '-username' and '-password' flags are given, only those credentials can be used for authentication Additional users can be added via the ssoadmin APIs or using govc for example: % govc sso.user.create -p password govc Closes vmware#2852
The ssoadmin endpoint is now used for authentication for both SOAP and REST endpoints. Previous behavior is retained: - By default, any non-empty username + password is authenticated - If vcsim '-username' and '-password' flags are given, only those credentials can be used for authentication Additional users can be added via the ssoadmin APIs or using govc for example: % govc sso.user.create -p password govc Closes vmware#2852
The ssoadmin endpoint is now used for authentication for both SOAP and REST endpoints. Previous behavior is retained: - By default, any non-empty username + password is authenticated - If vcsim '-username' and '-password' flags are given, only those credentials can be used for authentication Additional users can be added via the ssoadmin APIs or using govc for example: % govc sso.user.create -p password govc Closes vmware#2852
The ssoadmin endpoint is now used for authentication for both SOAP and REST endpoints. Previous behavior is retained: - By default, any non-empty username + password is authenticated - If vcsim '-username' and '-password' flags are given, only those credentials can be used for authentication Additional users can be added via the ssoadmin APIs or using govc for example: % govc sso.user.create -p password govc Closes #2852
The ssoadmin endpoint is now used for authentication for both SOAP and REST endpoints. Previous behavior is retained: - By default, any non-empty username + password is authenticated - If vcsim '-username' and '-password' flags are given, only those credentials can be used for authentication Additional users can be added via the ssoadmin APIs or using govc for example: % govc sso.user.create -p password govc Closes vmware#2852
Is your feature request related to a problem? Please describe.
While looking at vcsim to do some user/group creation automation testing I noticed that only a few of the SSO features are implemented in vcsim but not user/group creation. Here are two examples of the API calls using govc commands:
output of each command in vcsim docker container:
Describe the solution you'd like
Having the sso API calls that govc provides available in vcsim as well:
Describe alternatives you've considered
Only alternative I can think of is using an actual vCenter server instance to test the SSO user/group creation.
Additional context
Thank you for creating this vcsim tool, it is really really helpful for testing things out without requiring a actual vCenter server instance. I'm using the container flavor but I'm sure the other flavors are similarly useful to the community.
The text was updated successfully, but these errors were encountered: