> For the complete documentation index, see [llms.txt](https://docs.openiam.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openiam.com/troubleshooting/signing-in/access-forbidden.md).

# Access forbidden error

An Access Forbidden error in the browser when every service is healthy, which is a stale authorization graph rather than a service fault.

| Symptom                                                                                                                                   | Likely cause                                                                       | Resolution               |
| ----------------------------------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------- | ------------------------ |
| `Access Forbidden` in the browser, every service up, nothing in `auth-manager.log`, authorization errors in the reverse proxy's error log | The authorization graph does not yet reflect the content provider you just created | Rebuild the graph, below |

This turns up on a new deployment, in the sequence: change the `sysadmin` password, answer the challenge questions, create a content provider — and the next attempt to reach the Webconsole is refused.

The combination is what identifies it. **All OpenIAM and infrastructure services are up**, there are **no exceptions in `auth-manager.log`**, and the authorization errors appear only in the reverse proxy's error log. Nothing is broken; the graph that effective access is computed from has not caught up with the new content provider.

## Rebuild the authorization graph

{% code overflow="wrap" %}

```bash
curl http://127.0.0.1:9080/openiam-esb/authmanager/rebuildGraph
```

{% endcode %}

**On an HA installation, run it on every node.**

The request returns as soon as the rebuild is queued rather than when it finishes, so give it a moment and try the Webconsole again. See [Rebuild the authorization graph](/administration-guide/operations/rebuild-the-authorization-graph.md) for what the `auth-manager` log says about a rebuild that finished and one that failed.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.openiam.com/troubleshooting/signing-in/access-forbidden.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.