Generic login
Store a sign-in address, login and password for any site or service when no card fits.
Connect it with: User name and password. Generic login's own documentation: https://datatracker.ietf.org/doc/html/rfc7617.
What agents can do
Connect Generic login so the agents working your tasks can reach it. With it connected, they can:
- Sign in to the site at the URL you saved, with the login and password, in tasks allowed to use the secret.
- Use the login for a tool or script that asks for a user name and password, without anyone pasting them into a prompt.
Before you start
- An account on the site or service, with its sign-in address, login and password.
- A login without two-factor sign-in, or with its TOTP seed saved in 2FA seed so an agent can enter the code.
- A Jaah account. Anyone can add a personal secret; an organization secret needs an Org Owner or Admin.
Connect with Generic login
Jaah connects to Generic login with a user name and password, not with a sign-in button.
Connect with an API key
Find each value first:
- URL: The address where you sign in, for example https://example.com/login, so agents know which site the login is for.
- Login: The user name or email address you sign in with.
- Password: The password for that login. Jaah stores it encrypted and never shows it again.
- 2FA seed (optional): The base32 TOTP seed shown when the account set up two-factor sign-in, if it uses one. Never put it in the description: every task that may use the secret reads that.
Then add it to Jaah:
- In Jaah, open Secrets, select New, and pick the Generic login card.
- Name the secret and choose who can use it.
- Fill in URL, Login, Password, 2FA seed.
- Select Save. Jaah tests the secret straight away (see Test the connection).
Jaah encrypts what you type and never shows it again — not to you, and not to an admin.
Use your own OAuth app
Not used: Jaah connects to Generic login with a user name and password, not through an OAuth app.
Test the connection
Select Test on the secret. Jaah makes one read-only call to Generic login with the stored values and shows the result on the secret's page. Jaah also tests automatically when you save or reconnect.
Who can use it
Every secret has an owner, and the owner decides who can use it:
- Personal — only your own tasks can use it. This is the default.
- Organization — every task in the organization can use it. Only Org Owners and Admins can choose this.
- Attached to a project — every task on that project can use it, whoever started the task. See Attach a secret to a project.
More on owners and access: How secrets work.
Use it in an agent session
An agent asks for the secret with its credential_get tool, by the secret's path, when it needs it, and gets the values for that one call. The path is the owner's prefix and the secret's name:
org/<name>for an organization secret,projects/<project>/<name>for one attached to a project,me/<name>for your personal one.
A key connection hands the agent its fields: base_url, login, password, totp_seed.
Tell the agent in your task description which secret to use, for example “use the Generic login secret org/generic-login”.
Manage, rotate or disconnect
Everything is on the secret's page under Secrets:
- Rotate a key: create a new key at the vendor first, then select Replace on the secret and paste it. Revoke the old key at Generic login once the test passes. Steps: Replace or delete a secret.
- Disconnect: select Delete. The stored values are destroyed and agents lose access on their next call. To end access at Generic login's side too, change the password at Generic login or remove the user.
Limitations
- There is no Test: a URL, login and password do not say how the site signs in (a form, single sign-on or HTTP Basic), so any test would be a guess.
- A site that asks for a captcha, or a second factor other than a TOTP code, blocks an agent at sign-in.
- Agents can do only what the connected Generic login account allows.
Troubleshooting
The secret shows no Test button
Expected: a generic login cannot be tested. Check it by signing in once yourself with the same login.
An agent reports the sign-in failed
Sign in yourself at the saved URL with the same login. If the password changed, open the secret and replace it; if the site now asks for a second factor, use a service account without one.
Still stuck? Select Test and read the result: it names the value Generic login refused and the status it answered.
FAQ
When should I use this card instead of a service's own card?
Only when the service has no card. A service's own card knows how it signs in and can test the secret.
Can I store an API key here?
No. Use Generic API key, which records the header and prefix the key is sent under and can test it.
Can Jaah or an admin see the key or token?
No. Jaah stores it encrypted and never shows it again. Only the tasks allowed to use the secret receive it, at the moment they ask for it.
Can I connect more than one Generic login account?
Yes. Add one secret per account, each with its own name, and tell the agent which one to use.