Remove Cloud Connector "enabled" checks
We have multiple code paths that try to obtain a token purely to check whether CC/Duo is "enabled". This is not correct anymore.
Historically, for the self-managed/dedicated customers the token was synced with different cadence than cloud connector "access data" (entitlements), which could cause that user permission check returns true, and the token is not yet synced from CDot.
This is not the case anymore, and permission check (user.allowed_to_use) should be sufficient.
Also the enabled check does't make sense for gitlab.com as it would self-issue a token, check if it exists, and then when sending request, it would self issue a new token.
This happens in the following modules:
-
Code Suggestions Client: UJWT path - !193779 (merged) -
LLM Docs Client -
Anthropic Client - !193777 (merged) -
VertexAi Configuration - !193799 (merged) -
X-ray scans - !193782 (merged)
Proposal
All enabled checks should be removed, as not necessary and redundant.
Progress 24-06-2025
All MRs are in review, once they are merged this issue will be completed