> 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/activationlink.md).

# Error when sending activation link

Why an activation link does not arrive, and the separate property that governs whether the auto-generate option appears on the Reset Password screen.

| Symptom                                                                          | Likely cause                                                                                                          | Resolution                                                                                            |
| -------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ----------------------------------------------------------------------------------------------------- |
| **Send Activation Link** is chosen and the link never arrives                    | Mail is not being delivered. An activation link is an ordinary notification, so it fails the way any other mail fails | [Mail and notifications](/administration-guide/platform/mail-and-notifications.md#when-it-goes-wrong) |
| **Auto-generate Password** is missing from the **Reset Password Action** choices | `org.openiam.ui.user.reset.password.option.autoGenerate.show` has been turned off                                     | [Turn the option back on](#turn-the-option-back-on)                                                   |

## These two are not related

An earlier version of this page reported them as one fault: that hiding the auto-generate option also stopped the activation link completing. **That does not hold on a current release, and the screen makes it clear why.**

**Reset Password Action** offers three cards — **Set Password Manually**, **Auto-generate Password** and **Send Activation Link**. Only the middle one is governed by the property. The manual and activation-link cards are rendered unconditionally and stay selectable whatever it is set to; the property changes nothing but whether the third card is there and how wide the other two sit. Nothing on the server couples them either.

So if the link is not arriving, the auto-generate setting is not the reason, and turning it on will not fix it. Treat it as mail that did not get delivered.

## Turn the option back on

This is for the second symptom only — the auto-generate action missing from the screen.

`org.openiam.ui.user.reset.password.option.autoGenerate.show` **ships `true`**, so a deployment missing the option has had it turned off.

{% stepper %}
{% step %}
**Open the setting.** It is on **Administration** → **System Configuration**, labelled *Show 'Auto-Generate Password' Option on Reset Password Page*. Set it to `true`.
{% endstep %}

{% step %}
**Confirm it reached the screen.** **Reset Password Action** should now offer all three cards instead of two.
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**If the screen shows `true` and the option still does not appear**, something else is supplying the value. A property can come from four sources, and an `OPENIAM_PROP_*` environment variable on a container overrides the Webconsole invisibly — see [System property reference](/administration-guide/reference/system-properties.md).
{% endhint %}


---

# 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/activationlink.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.