access sign-in roles keycloak administration

Signing in, roles and platform administration

How access works: one identity service, membership of a league, roles within it, and the separate plane that decides which leagues exist.


Signing in

Each league is reached at its own address — wjfl.league360.co.uk — and the sign-in page there has no email field and no password field. The portal is a relying party on a separate identity service: it stores no passwords and has no registration or password reset of its own. Continue to sign in hands you to that service and the browser comes back signed in.

Signing out ends the session at the identity service as well as locally, so the next click does not silently sign you back in.

Membership and roles are two different things

Access to a league needs both, and they fail differently.

  • Membership of the league. Without it the sign-in is refused outright and no session is created — the page says Not a member of this league.
  • A role within that league. With membership but no relevant role you are signed in and the members area is closed to you — the page says You do not have access to this and lists the roles you do hold.

Roles do not cross leagues. A club secretary whose club runs teams in two leagues has one account and separate roles in each; holding League Administrator in one grants nothing in the other. That is deliberate and it is why roles are recorded per league rather than against the person.

RoleReaches the members area
League AdministratorYes — everything, including the configuration a banding review needs
League SecretaryYes
Fixtures SecretaryYes — the structure, readiness, reviews and publications
Discipline SecretaryYes
TreasurerNo. A full member of the league who can see the structure and never a rating or a banding review

The Treasurer case is the one to understand: a league-wide role is not the same as an administrative one, and being trusted with the league’s money says nothing about whether you should see what the engine thinks of a nine-year-old’s team.

Platform administration is a separate plane

Deciding which leagues exist is not a league role. It lives at admin.league360.co.uk, which resolves no league at all: sign in there and you get the list of leagues on the deployment and the ability to add one. You get no access to any league’s data — reaching a league’s content means signing in to that league, on its own address.

It is the same identity service and the same accounts; what separates the two is a dedicated administrator role held by the person, honoured only on that host. The reverse holds as well: an account with that role signing in to a league is only what that league’s roles say it is.

Signing in there without the role gets you Not a platform administrator, naming the role that is missing.

A new league needs setting up in two places

Provisioning a league in the portal does not by itself let anyone sign in to it. The identity service needs its own entries — the league’s address, and a group for the league with role groups beneath it — before its officers can get in.

If a sign-in button appears to do nothing, or refuses you from a league you administer, that is the usual cause. The pages name what is missing when this happens.