Signin
/api/v2/signinCreate a user session.
Authenticates Basic authentication credentials for a user, and then, if successful, generates a user session.
To authenticate a user, pass the HTTP Authorization header with the
Basic scheme and the base64-encoded username and password.
For syntax and more information, see Basic Authentication for
syntax and more information.
If authentication is successful, InfluxDB creates a new session for the user
and then returns the session cookie in the Set-Cookie response header.
InfluxDB stores user sessions in memory only. They expire within ten minutes and during restarts of the InfluxDB instance.
User sessions with authorizations
- In InfluxDB Cloud, a user session inherits all the user’s permissions for the organization.
- In InfluxDB OSS, a user session inherits all the user’s permissions for all the organizations that the user belongs to.
Related endpoints
Parameters
Header parameters
Zap-Trace-Span
stringcurl --request POST \
"https://us-east-1-1.aws.cloud2.influxdata.com/api/v2/signin" \
--header "Authorization: Bearer INFLUX_TOKEN"Responses
Set-Cookie response header contains the session cookie.Unauthorized. This error may be caused by one of the following problems:
- The user doesn’t have access.
- The user passed incorrect credentials in the request.
- The credentials are formatted incorrectly in the request.
code
required
stringinternal error
, not implemented
, not found
, conflict
, invalid
, unprocessable entity
, empty value
, unavailable
, forbidden
, too many requests
, unauthorized
, method not allowed
, request too large
, unsupported media typeerr
stringmessage
stringop
stringcode
required
stringinternal error
, not implemented
, not found
, conflict
, invalid
, unprocessable entity
, empty value
, unavailable
, forbidden
, too many requests
, unauthorized
, method not allowed
, request too large
, unsupported media typeerr
stringmessage
stringop
stringcode
required
stringinternal error
, not implemented
, not found
, conflict
, invalid
, unprocessable entity
, empty value
, unavailable
, forbidden
, too many requests
, unauthorized
, method not allowed
, request too large
, unsupported media typeerr
stringmessage
stringop
stringWas this page helpful?
Thank you for your feedback!
Support and feedback
Thank you for being part of our community! We welcome and encourage your feedback and bug reports for InfluxDB and this documentation. To find support, use the following resources:
Customers with an annual or support contract can contact InfluxData Support.