CAPIT CONNECT
Sign-in for your visitors, without building it yourself
One “Sign in with CAPIT” button on your site: visitors choose Google, Apple, Facebook, LinkedIn, Snapchat or their email address in a CAPIT box showing your name and logo. You receive a verified identity through the OpenID Connect standard.
1 month free, no card needed · Then €5 per month, no commitment: unlimited sign-ins and Jeanne’s assistance included.
- Six sign-in methods without creating the Google, Apple, Facebook, LinkedIn and Snapchat apps yourself.
- OpenID Connect standard: every common library works (PHP, Node, Python, WordPress…).
- A box with your site’s name and logo, and clear visitor consent.
- Jeanne, our AI assistant, helps with integration and reads your configuration errors.
In three steps
- Create your application in the console: name, logo, https redirect addresses.
- Copy the identifier and secret into your OpenID Connect library.
- Add the button: visitors sign in, you receive their identity.
Integration documentation
CAPIT Connect is a standard OpenID Connect provider. Give the discovery address to your library: it finds the endpoints and keys by itself.
Discovery address
https://connect.capit.net/oidc/.well-known/openid-configuration
Endpoints
| issuer | https://connect.capit.net/oidc |
|---|---|
| authorization_endpoint | https://connect.capit.net/oidc/auth |
| token_endpoint | https://connect.capit.net/oidc/token |
| userinfo_endpoint | https://connect.capit.net/oidc/me |
| jwks_uri | https://connect.capit.net/oidc/jwks |
| end_session_endpoint | https://connect.capit.net/oidc/session/end |
| revocation_endpoint | https://connect.capit.net/oidc/token/revocation |
Supported flow
- Authorization code (response_type=code); PKCE S256 required for a public application (browser, mobile), recommended otherwise.
- Application authentication: client_secret_basic or client_secret_post; none for a public application.
- Scopes: openid, email (email, email_verified), profile (given_name, name, locale). ID token signed RS256.
- sub is unique to your application: it is the identifier to store; it cannot be matched with any other site.
- Lifetimes: code 5 minutes, access token and ID token 1 hour.
- Click-free recognition: from the origin of a registered redirect address, GET https://connect.capit.net/connexion/sso/statut (credentials: 'include') returns {"connecte": true|false}; if true, start sign-in with prompt=none: the code comes back with no screen (after the first consent).
Examples
PHP (jumbojett/openid-connect-php)
<?php
require 'vendor/autoload.php';
use Jumbojett\OpenIDConnectClient;
$oidc = new OpenIDConnectClient('https://connect.capit.net/oidc', 'cc_VOTRE_CLIENT_ID', getenv('CAPIT_CONNECT_SECRET'));
$oidc->setRedirectURL('https://votre-site.example/auth/retour');
$oidc->addScope(['openid', 'email', 'profile']);
$oidc->setCodeChallengeMethod('S256');
$oidc->authenticate(); // redirects to CAPIT Connect, then validates the response
$sub = $oidc->getVerifiedClaims('sub'); // stable identifier for your site
$email = $oidc->getVerifiedClaims('email');Node.js (openid-client 6)
import * as client from 'openid-client';
const config = await client.discovery(new URL('https://connect.capit.net/oidc'), 'cc_VOTRE_CLIENT_ID', process.env.CAPIT_CONNECT_SECRET);
// login route
const verifier = client.randomPKCECodeVerifier();
const url = client.buildAuthorizationUrl(config, {
redirect_uri: 'https://votre-site.example/auth/retour', scope: 'openid email profile',
code_challenge: await client.calculatePKCECodeChallenge(verifier), code_challenge_method: 'S256',
});
// callback route (keep verifier in the user's session)
const tokens = await client.authorizationCodeGrant(config, currentUrl, { pkceCodeVerifier: verifier });
const { sub, email, given_name } = tokens.claims();Python (Authlib + Flask)
from authlib.integrations.flask_client import OAuth
oauth = OAuth(app)
oauth.register('capit', client_id='cc_VOTRE_CLIENT_ID', client_secret=os.environ['CAPIT_CONNECT_SECRET'],
server_metadata_url='https://connect.capit.net/oidc/.well-known/openid-configuration',
client_kwargs={'scope': 'openid email profile', 'code_challenge_method': 'S256'})
@app.route('/login')
def login():
return oauth.capit.authorize_redirect('https://votre-site.example/auth/retour')
@app.route('/auth/retour')
def retour():
user = oauth.capit.authorize_access_token()['userinfo'] # sub, email, given_nameWordPress
Plugin « OpenID Connect Generic Client »
Client ID: cc_VOTRE_CLIENT_ID
Client Secret Key: (secret from the console)
OpenID Scope: openid email profile
Login Endpoint URL: https://connect.capit.net/oidc/auth
Userinfo Endpoint URL: https://connect.capit.net/oidc/me
Token Validation URL: https://connect.capit.net/oidc/token
End Session Endpoint: https://connect.capit.net/oidc/session/end
Redirect URI to declare in the console: https://votre-site.example/wp-admin/admin-ajax.php?action=openid-connect-authorizeThe button
Point this link to the route of your site that starts sign-in (it redirects to CAPIT Connect).
<a class="capit-connect-btn" href="/auth/capit">
<svg width="20" height="20" viewBox="0 0 24 24" aria-hidden="true"><rect width="24" height="24" rx="6" fill="#653b88"/><path d="M15.5 8.2a5 5 0 1 0 0 7.6" fill="none" stroke="#fff" stroke-width="2.2" stroke-linecap="round"/></svg>
<span>Sign in with CAPIT</span>
</a>
<style>
.capit-connect-btn{display:inline-flex;align-items:center;gap:10px;padding:10px 18px;border:1px solid #d6cfe0;border-radius:999px;
background:#fff;color:#2b1d3a;font:600 15px/1 system-ui,sans-serif;text-decoration:none}
.capit-connect-btn:hover{border-color:#653b88}
</style>Test page
Each application can allow CAPIT’s test page: one click in the console lets you try the sign-in box before writing any code. Without a subscription, only the test page works.
Security
- https redirect addresses compared exactly: no wildcard, no fragment, no IP address.
- Secret shown only once, stored as a hash; rotation with a 24-hour overlap.
- Log of sign-ins and errors in your console, kept for 13 months.
- Rate limiting; shared CAPIT session: a member already signed in has nothing to retype, and their consent is asked only once per site.
Jeanne’s assistance
Jeanne answers your integration questions with the best available AI model; she sees your applications’ settings (never the secrets) and their latest errors. Included in the subscription, up to €1 of cost per month.
Personal data
Your site only receives the identifier unique to your application, the email address and the first name, after the visitor agrees. CAPIT acts as your site’s processor for authentication; you remain the controller of the data you receive.
