Authentication

The following is a list of authentication issues you may encounter when using OpCenter.

Why does float login return 'Get "https://127.0.0.1/api/v1/login": dial tcp 127.0.0.1:443: connect: connection refused'?

Incorrect IP address for OpCenter or the OpCenter IP address has aged out of the local float cache. Check OpCenter IP address and try again with float login -a <ip_address>

float command returns "Error: Session timeout (code: 2001)". Why?

Current OpCenter session timed out. Log in to OpCenter again.

float image add or float submit returns "Error: Authentication failed, incorrect username or password (code: 2003)". Why?

This indicates an attempt to access private repository with incorrect or missing credentials. Rerun command with valid credentials to access repository.

Each SAML user has a profile that includes username as an attribute. After changing the username, I notice that the OpCenter creates a new user with new username even though it is the same user. Why?

In the SAML server, a user is identified by the entire set of attributes including username. In the OpCenter, a user is identified by username only, so if username changes, the OpCenter keeps the existing user and creates a new user identified by the new username.