Forge a client
One provider, one identity, and as many clients as there are ways of asking. Every
choice below is read from the document https://op.spk.li publishes: what it does not
announce is not offered here. The client is registered the moment you build it (RFC 7591), signs
the user in, and deletes itself when you are done with it (RFC 7592).
Presets
21 compositions written down. A preset fills the form below, and building it replaces the client of the same name.
Posted response
Gets the code in a POST rather than in the URL, and its secret in the body.
FAPI 2.0 with DPoP
Pushes a signed request, reads a signed response, holds a token bound to its key.
Secret-signed assertion
Signs an assertion with its secret instead of sending the secret.
Self-signed certificate
Proves who it is with a certificate it published itself (mTLS).
Bound to a key
Holds a token useless without its key: every call carries a proof (DPoP).
Signed, encrypted UserInfo
Gets UserInfo as a JWT, signed by the provider and encrypted to it.
Front-channel logout
Is told of a logout in the browser, by a frame the provider loads.
Clients this browser has built
| fapi |
JC6zyTTaIc69lswo6_sNt0-6KnPCsl1eE-N8xONuERI · Forged: FAPI 2.0 with DPoP
Take it apart
|
|---|---|
| backchannel |
P20lndlnw4sW5iSBvhQHP2uuUT7-jQx4lbAn16UiTxc · Forged: back-channel logout
Take it apart
|
| frontchannel |
NAmAwOaXvi7BPoZXXbx09-9ej71x0YHLIMgdhPOegQ4 · Forged: front-channel logout
Take it apart
|
| userinfo-jwt |
XzyPyIK32ONlQkm8Fv7GC7PA87lf2fJKq9Y5fM1mLro · Forged: a signed and encrypted UserInfo
Take it apart
|
| encrypted-id-token |
tQh16ErY5-9N1n3PUhTKJ0g9TNb3U_zFxBkYylsjAYw · Forged: an encrypted ID token
Take it apart
|
| refresh |
1i1uYjY5yH8ciz_2xd9KzhvvsN_vAtA4rRncXqeeqDI · Forged: a refresh token
Take it apart
|
| dpop |
WOucwsOo8yEHKsiX3usztRdEspfMJUxzLNvpm_-uGIg · Forged: a token bound to a key
Take it apart
|
| key |
kD5Xt1PDHk7r5Z309eWtxrpkpVTD5gCTspEJBL0tFZs · Forged: a key instead of a secret
Take it apart
|
| secret-jwt |
m6iSGGFmqucf3h0Ytgwp8I8JUBgSpc9LDq7heOmV4gE · Forged: an assertion signed with the secret
Take it apart
|
| public |
cgFnUuTT1ggW9JNe6mUBJtL-ANzWRoOVkZKCexvn0_w · Forged: no credential at all
Take it apart
|
| pairwise |
OUixtNBCcxtEt7JwmgxxA6r2utQoYoKX3tCG4Flke1c · Forged: a sub of its own
Take it apart
|
| jar |
LkMH6kCbqJFqySNMaxx-tf4vbTo9eTTnSiErzax7RYo · Forged: a signed request
Take it apart
|
| par |
2M24n76rBK3ocDMySv5ZxwSW8r3C-o9gWDDO8yC4N5c · Forged: a pushed request
Take it apart
|
| jarm |
qc42001zD4B9M9Pzn82pbHx8LYuOxWPRBQYDF4Otpr0 · Forged: a signed response
Take it apart
|
| form-post |
T1romGtRWjEm4sEHAvGY1DmQy8dd16qr24NuGUpmPeg · Forged: a posted response
Take it apart
|
| basic |
BX_fadezT6U8dxyQ7n20edeSPJiKEjHYTCF7gZ3adPs · Forged: everything in the open
Take it apart
|
Compose one
What a client cannot ask for
Seven members of this provider are not offered above, and that is the rule and not an omission: they are written by whoever declares a client in the configuration, or by the registration policy of the tenant, and a client that registers itself is refused rather than obeyed. A client that comes from nowhere gets nothing a declared client does not get by asking for it (decision 0009).
access_token_format | the shape of the access token, self-contained or opaque |
|---|---|
resources | the resources it may ask a token for (RFC 8707 §2); a client that registers none asks for none |
require_sender_constrained_tokens | that its tokens are never bearer tokens (FAPI 2.0 §5.3.1) |
requires_consent | that the consent page may be skipped for it |
requires_pkce | that PKCE may be dispensed with (decision 0017) |
token_exchange | what it may exchange a token for (RFC 8693 §2.1) |
may_act | who may act for the subject of its tokens (RFC 8693 §4.4) |
So the shape of the access token is the tenant's, and the page of a built client reads
it off the token it was issued rather than off what it asked for. The two shapes are seen on the
clients the configuration declares, which castor demo --resource-server signs in
as.
What has no browser
Some flows of the provider are never clicked, because no browser of this application
goes into them: the client is a program, or it is the provider that calls the client back. They are
played from the command line of the provider's repository, castor demo --device,
--ciba, --service, --assertion, --native and
--push, and each one asserts every step. The forge composes a client of the
authorization code grant, which is the one a browser plays.