> 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/end-user-guide-for-selfservice/change-password/security-keys.md).

# Security keys

Register a security key or built-in authenticator so you can sign in without a password.

A **security key** proves it is you without a password. It can be a small physical device you plug in or tap, or something already built into your laptop or phone — a fingerprint reader, face recognition, or a screen-lock code. These use the FIDO standard, so the same key works across services that support it.

Open **Security Keys** from your account menu → **Security → FIDO Authenticator**.

## Why use one

* **Harder to steal.** There is no password to be guessed, phished, or reused from another site. The secret never leaves the device.
* **Faster.** A tap or a fingerprint instead of typing.
* **Phishing-resistant.** A key checks which site is asking, so a convincing fake page cannot use it.

Your organization may offer this as an option, or require it.

## Registering a key

{% stepper %}
{% step %}
**Open the Security Keys page and choose to add a key.**

If you have none yet, the page reads *"No security keys registered"*.
{% endstep %}

{% step %}
**Follow your browser's prompt.**

Your browser — not OpenIAM — runs this part, so the wording depends on your browser and device. You will be asked to insert and tap a key, scan your fingerprint, look at the camera, or enter your device PIN.
{% endstep %}

{% step %}
**Give the key a recognisable name.**

If you register more than one — say a laptop and a USB key — names are how you tell them apart later. "Work laptop" is more useful than "Key 2".
{% endstep %}

{% step %}
**Confirm it appears in the list.**

You can now use it to sign in.
{% endstep %}
{% endstepper %}

## Removing a key

Select the key and delete it. You are asked *"Are you sure you want to delete the selected key?"* because the action cannot be undone — a removed key must be registered again from scratch.

Remove a key when you stop using that device, and **immediately** if it is lost or stolen.

{% hint style="warning" %}
Register **two** keys if your organization allows it — for example your laptop and a separate physical key. If you rely on a single key and lose it, you may be locked out until the help desk can help. A second key is your way back in.
{% endhint %}

## If it doesn't work

* **Your browser doesn't offer the prompt.** Older browsers may not support security keys. Try an up-to-date browser.
* **The key isn't recognised.** Make sure it is properly inserted, and that you tap it when it flashes.
* **It works on one computer but not another.** A key built into a device (fingerprint, face) only works on *that* device. A separate physical key travels with you.
* **You've lost your only key.** Contact your help desk — this is exactly the situation they expect.


---

# 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/end-user-guide-for-selfservice/change-password/security-keys.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.