-
Notifications
You must be signed in to change notification settings - Fork 4
Loadable NameID builder
Paul Lemmers edited this page Jun 1, 2020
·
2 revisions
Some institutions require more/different algorithms to build a NameID for the AuthnRequest to the SFO gateway.
- Assembly loading in the OnAuthenticationPipeLineLoad() method. To avoid assembly loading problems during registration (registration does not call this method).
- Initialization with the full adapter set of attributes. Per adapter instance an instantiation of the NameID builder class (to allow for per instance member variables, although probably not required for most builders).
- Real call with the the original identity claim.
- Logging through log4net with constructor dependency insertion.
- Low level interface to allow for anything.
- Base class which already does the AD query and has an abstract method for attribute combination logic.
Interface and base class in the Adapter. Separate project in the solution with a console application to test assemblies. After cloning the repository, changing the namespace and the attribute combining method is enough. With the console application they can test if it works. If it does then adding it to the real Adapter/plugin should work.
- The setup/configuration program. It does not know about the attributes that the loadable NameID assembly requires. Reading and writing a dictionary from/to attributes is simple. However, the current Setting class is a single string. And the current adapter part has multiple strings (not a single dictionary).