Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated to match current implementation and also announce changes coming in Q1


Excerpt

The FS BAS API is and Sebra APIs are used to import administrative users from FS



Once every 24 hours (at night European time) we check for all users returned by FS

...

In order to import a user from FS BAS, the following fields must be filled out for that user:

  • first name
  • last name
  • work and/or home email (work email is prioritized, and we only save one of them)
  • username
  • active/inactive status

We then check the following:BAS/Sebra:

  • Is there an existing IA user with the same FS Person ID (løpenummer) as the user? (Support for Person ID is being rolled out gradually in Q1 2018)
  • Is there an existing IA user with the same FEIDE username as the user?
  • Is there an existing IA user with the same email (work or home)?

If the answer to both all of the questions above questions is "no", then we import the user. Otherwise, we simply log that there is already an existing IA user that corresponds with the BAS user

When we create the internal user we populate the following fields with data from BAS/Sebra:

  • first name
  • last name
  • work and/or home email (work email is prioritized, and we only save one of them)
  • username
  • active/inactive status


If an existing match is found, we update the active/inactive status, and populate that user with SSN/NIN and FS Person ID.

Note that support for updating users based on email matching is being rolled out in Q1 2018.


For more information, view https://www.fellesstudentsystem.no/dokumentasjon/teknisk/fsws-dok/rest/bas.html


Image Removed