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
Currently, Swift Permanent Storage considers that the Token generated by the keystone does not expire. However, the token expires and may even be invalidated in the identity service. Therefore, it is necessary to refresh the token when trying to make a request to Swift and receive the expired token response.
Swift's CLI allows you to receive credentials (projectId, userId, userPassword) and it is responsible for generating a token to perform the operation. Therefore, as a token is generated for each operation, we will never have an expired token in use.
Currently, Swift Permanent Storage considers that the Token generated by the keystone does not expire. However, the token expires and may even be invalidated in the identity service. Therefore, it is necessary to refresh the token when trying to make a request to Swift and receive the expired token response.
Swift's CLI allows you to receive credentials (projectId, userId, userPassword) and it is responsible for generating a token to perform the operation. Therefore, as a token is generated for each operation, we will never have an expired token in use.
Be based on: ufcg-lsd/saps-engine#132
The text was updated successfully, but these errors were encountered: