ScoutID in English

Single Sign On

Button logo with ScoutID
When you see this symbol, you know they support logging in using ScoutID.

In order to be able to offer more and better web services without increasing the amount of login information you need to keep track of, we have introduced the ScoutID service. ScoutID means that you who are a member of the Scouts only need to keep track of one login to access most of our websites and e-services.

Initially, ScoutID is only available to you who are a member of an ”direktansluten scoutkår”, but our ambition is that the collaborating organizations that are interested should also be connected and be able to use the same login solution.

For Scout group (kår) and Service Providers

The system offers login both for the Scouterna’s central services (scout-group-sites, web courses, etc.) and for external services. What is required is that your service supports the SAML2-protocol or JWT-tokens, which are easily added with plugins and libraries for most common frameworks and content management systems.


We can configure ScoutID so that all members of the Scouterna can log in to your service, or control so that only those who meet certain criteria are given access. You also have the option of doing your own filtering based on data about the logged in user:

  • Membership in Scout groups, department, and patrol
  • Roles in organization, district, Scout group, department, and patrol
  • Age
  • Name and email address
  • Member number (unique ID)


If you have a project that addresses all or some of the Scouts’ members and wants to offer a simple login, contact us at and we will see How we proceed!

Generic JWT

Can be used for javascript frameworks such as react and vue.


  • Your project is online¹ and connected via https.
  • Your project has a backend that can verify JWT tokens with asymmetric RS256 key.

How our JWT setup works

The JWT solution is built on top of the SAML2 solution, so:

  • Your project makes an ajax request and asks if the user is logged in at ScoutID.
  • If the user is not logged in, you will receive a url in the answer, where you can send the user to log in (where a SAML2 login is made),
  • After the user logs in at ScoutID, the user lands in your project again. (on a url configured in ScoutID).
  • Your project resends an ajax request and asks if the user is logged in ScoutID.
  • You will receive a JWT token as response, whit a validity period of 15 minutes, after these 15 minutes you will have to renew / request a new one, which you will receive if the user is still logged in ScoutID.
  • This JWT token can then be sent to your backend. In the backend you verify that the token is valid, if it is has expired, it is recommended that you answer with an error code 498, and that you then in the frontend automatically retrieve a new token, and resend the request to your backend.
  • Since the token contains the information about memberships and more (see above), your backend does not need to keep track of sessions.

Code Exemaple

const login = async () => {
   const response = await fetch("" + location.hostname, {credentials: 'include'});
   if(!response.ok) throw response;
   const result = await response.json();
   if(!result || !result.ok || !result.token) {
      throw result;
   return result.token;



Our current public RS256-key

-----END PUBLIC KEY-----


Contact to request help from us.

Generic SAML2


  • Your project is online¹ and connected via https.
  • You can add and configure a library/plugin that supports adding SAML2-login / SAML2-Identity-Provider

What information do ScoutID need from you

To set up your project as a Service-provider in the ScoutID konfiguration, we need to register 3 values:

  • Name, a name so we can easy find your project in the list.
  • Entity-id, the identifier your library sends to ScoutID to identify your project, it depends on the library you using, but the most common is the domain ”” or the URL ””. If you try to login with ScoutID before we added your Entity-id to the whitelist, the error message includes the Entity-id your project tried to use.
  • ACS, an url for Assertion-Consumer-Service
  • SLS, an url for Single-Logout-Service-URL, may be the same URL as ACS.

We can also add extra filtering option, but if your library also can do filtering, its recomended that you kepp the filter configuration in your project, so you have full controll over it.

What your project needs from ScoutID

  • In SAML terms, ScoutID is a IDP, IDentity Provider, so you need to add us as IDP in your project.
  • You also need to add us as trusted a IDP, by adding our certificate to your project.
  • You need to tell your project the location of us, our SSO, Single Sign On, url is:
  • Some libraries instead of the SSO-url, require you to add ”metadata”, our metadata is located here:
  • Some libraries supports SLS, Single Logout Service, our SLS-url is:


Contact to request help from us.