corestack_ http_ auth_ get
HTTP authentication.
When to use it
A row's HTTP authentication: whether the whole environment is protected, the protected paths with their logins (never the passwords), and the set's version — which corestack_http_auth_update needs.
Ask for it
Using the Corefinity MCP server, call corestack_http_auth_get with site_id 4211. (HTTP authentication.) Tell me what it returned.Inputs
Any row: the site or one of its environments. At least 1.
Example call
{
"name": "corestack_http_auth_get",
"arguments": {
"site_id": 4211
}
}If it is refused
| Reason | What to do |
|---|---|
invalid_arguments | The arguments do not match the tool's input schema, or the Control Panel refused a field. Fix the fields named in the answer and call again. |
tenant_mismatch | The object does not exist or the token may not see it. Check the id. |
scope_required | The token lacks a scope this call needs. Open the link in the answer to add it, then call again. |
pin_refused | The grant is limited to chosen clusters, sites or environments, and this call is outside them. Open the link in the answer to widen it. |
rate_limited | Too many calls. Wait for the number of seconds the answer names. |
temporarily_unavailable | The Control Panel could not answer just now. Nothing was started; try again shortly. |
internal_error | Something went wrong on our side. Quote the trace id to support. |
The answer
{enabled, — never a password. apply.state is applying, failed or applied;
apply.detail.credentials says whether the last change's logins were checked: pending while it runs, verified,
unverified (the check failed), or unchecked — saved, but the check could not run (the site answered with its
maintenance page). With unchecked, apply.detail.credentials_note is the sentence the Control Panel shows: "Saved. We
have not been able to check it yet: open the site to confirm the login prompt appears." When apply.state is failed,
apply.error says why in the Control Panel's words — for example, that the environment does not hold the saved
passwords; retrying that change (corestack_operation_retry, the failed operation from corestack_site_operations_list)
writes them again.