One directory, one login, every tool.
VeiraHub connects your LDAP or Active Directory once, gives directory groups their roles in Codeveira, Veira Seal and VeiraForge, and logs people in to all three with one account. A tool that isn't connected works exactly as it does without it.
For the Codeveira Team tools
Add a tool in the hub to get a one-time enrollment token, then paste it into the tool.
| Tool | Where to connect it | What it takes from the hub |
|---|---|---|
| Codeveira | Settings → VeiraHub, on any licence | Admins, roles in each repository, team membership, its licence key |
| Veira Seal | veira veirahub connect | Admins, roles in each project, its licence key |
| VeiraForge | Settings → VeiraHub | Admins and roles in each project |
How it works
Set it up once; the tools keep themselves in step.
Connect the directory
Point the hub at LDAP or Active Directory. People log in with their directory password; the hub never keeps one.
Connect the tools
Each tool enrolls with a one-time token and publishes the roles it can give, and the projects, repositories and teams they apply to.
Give groups their roles
Map directory groups to those roles. Every tool checks in every minute, makes accounts before a first login and disables them when the directory says so.
What it does
The same philosophy as the rest of the Codeveira Team lineup: your data stays on your servers.
Your directory, once
Connect LDAP or Active Directory in the hub, with a connection test. The tools take the connection from the hub instead of each being set up on its own.
Groups become roles
Give a directory group a role in a tool — admin, a role in one Veira Seal project, a reviewer in one Codeveira repository — separately for every tool. Each change is previewed: who gains and who loses access.
Never locked out
A change that would leave a tool without an admin from the directory is refused. The hub's own emergency admin logs in with a password and an authenticator app.
One login for all three
The hub is an OpenID Connect provider: every connected tool gets a Log in with VeiraHub button, and logging out of a tool logs out of the hub too.
Keeps working when the hub is down
Each tool gets a configuration signed with the hub's Ed25519 key, pinned when it connected, and logs people in against the directory itself from it while the hub can't be reached.
Accounts that follow the directory
The hub syncs with the directory every 15 minutes and at each login. Someone the directory no longer has is disabled, never deleted — and a sync that would disable over 20% of the accounts waits for an admin.
Licences in one place
Keep Codeveira's and Veira Seal's licence keys in the hub: each tool takes its key with its settings and checks it itself, so the hub can't make one up.
A portal for everyone
People see the tools their groups get them into, and go straight to them.
An audit log you can export
Every login, change and sync, filtered and exported as CSV or JSON, kept a year by default.
Why VeiraHub
Teams that run more than one of our tools set up the same directory, the same groups and the same roles in each of them, and log in to each one separately. VeiraHub does it once, for all of them — without becoming one more place your passwords live.
It's free, from Codeveira Team, the makers of Codeveira, Veira Seal and VeiraForge.