You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 15, 2020. It is now read-only.
I have a RESTful service that queries OneView resources via python-hpOneView and I want to provide session resources in this service using OneView credentials. The simple scenario is, considering each RESTful service corresponds to a single OneView appliance:
the service knows OneView ip address;
the user post to the service a username+password combination; it creates a hpOneView client instance and gives back the x-auth-token on the service header
the user access other services resources passing x-auth-token header which is used to build another hpOneView client instance and perform requests.
I know that python-hpOneView POSTs username+password to OneView's /rest/login-sessions when creating a new client instance and I think that a similar approach can be used with the session token and a PUT request to validate it.
Would you consider providing this additional authentication in a near version?
The text was updated successfully, but these errors were encountered:
Scenario/Intent
I have a RESTful service that queries OneView resources via python-hpOneView and I want to provide session resources in this service using OneView credentials. The simple scenario is, considering each RESTful service corresponds to a single OneView appliance:
I know that python-hpOneView POSTs username+password to OneView's /rest/login-sessions when creating a new client instance and I think that a similar approach can be used with the session token and a PUT request to validate it.
Would you consider providing this additional authentication in a near version?
The text was updated successfully, but these errors were encountered: