Page Comparison

...

In short: the authentication method(s) will be hidden in the SSO menu for CustomerID agent using application using template system. Then a CustomerID protection configuration corresponding to the internal authentication method and the url where user should be forwarded within CustomerID will be created.

...

1. Create an SSO template for the smartlink usecase. Let's call the template smartlink.
   1. Open the file <SSO-install-dir>/ubilogin/custom/template.index and add a line 'smartlink = templates/smartlink.properties'
   2. Go to the directory 'templates'. There should be a file called default.properties. Make a copy of it with the name smartlink.properties
   3. Open the smartlink.properties file, it should contain olnly line '@import = sso7', and add a method menu rules definition 'methodmenu.rules  = smartlink.rules'
   4. Create a file in the templates directory called 'smartlink.rules' and add the following line to the file (replace DC=test with the proper dn suffix)
      1. dn: CN=eidm2,OU=eIDM Services,CN=Ubilogin,DC=test
      2. hide: win.ap.1
   5. Open the eidm agent view application object view in SSO management and add the smartlink template to the template field values. Do the same for the workflow agentapplication object. Check that both agents applications also have the win.ap.1 method enabled in the methods view.
2.  Create a protection configuration in CustomerID for the smartlink.
   1. Open the file <CustomerID-install-dir>/application/custom/protection.properties
   2. Each protection configuration is prefixed with protection.N, use the next available value for N in the smartlink configuration.
   3. Use the following configuration for the smartlink.protection
      1. protection.N.methods = win.ap.1
      2. protection.N.sso.template = smartlink
      3. protection.N.customeriduseronly = false
      4. protection.N.continue = https://<CID-baseaddress>/eidm2/wf/admin
3. Now accessing the URL https://<CID-address>/eidm2/wf/protection/N should take the user automatically to WinAP and then back to CustomerID administration interface. 

...