Service keys
Operator page
Developers and owners only. A service key lets a whole website act on behalf of every member. Treat it like a password.
This is how WordPress proves to FMS that it is really our website.
Create a key for WordPress
- Give the app a name that says where it runs (1). Optionally list the IP addresses allowed to use it, one per line (2). Leave the list empty to allow any address.
- Press create, then press generate key on the new app.
- Copy the key. It starts with
fms_sk_and is shown once and never again.
Add it to wp-config.php on the WordPress server, as Connect to FMS shows. The plugin has no box to paste it into.
The key is shown once
If you lose it, generate a new one and update WordPress. There is no way to read an existing key back.
Which environment a key belongs to
A key belongs to the environment it was generated in. It keeps working there, whatever the portal is switched to. Each key's row says Belongs to: Production or Belongs to: sandbox ….
| You see | It means |
|---|---|
| Belongs to: Production | Every request with this key reaches production |
| Belongs to: sandbox staging | Every request with this key reaches the staging sandbox |
| Copied from another environment — not usable here | A copy brought over with old data. It works nowhere here. Generate a new key |
A test website needs its own key
Generate a test website's key while the portal shows its sandbox. A key copied from production reaches production. See Sandboxes.
Revoking a key
Revoke stops it working immediately. Anything using it breaks at once, so have the replacement ready before you revoke.
The IP allow-list
If you fill it in and get the address wrong, WordPress will report that FMS knows the key but refused the request. Either add the right address or clear the list.