Compliance Requirement

We have a requirement which needs your help with the possible solutions from the Sterling Secure Proxy application with minimal impact (post deployment). Here is the requirement:

There is a portal called Connect portal where partners login with their MitId (electronic ID in Denmark) and post successful authentication.

a SAML token is generated at an external Identity Provider (IdP). This SAML token is passed back to the portal and the portal is opened.

The connect portal displays a variety of application tiles along with My File Transfer (MyfileGateway1.0) as one of the tiles.

When the user clicks on the My File Transfer tile then this SAML token is passed to the SSP’s SSO Signon page. Now,

there is a field named CVR (Org Number) present in the SAML token that needs to be passed Along with the login user and password

when the user clicks at sign-in on SSP’s SSO page. The login auth request goes to SEAS (As the users are externally authenticated),

at SEAS, the CVR that is passed should be validated against the login user in LDAP (whether the CVR is present for this user),

If the validation is successful then the sso token will be generated and passed back to SSP, to continue to access myfilegateway1.0 application. We really want to understand the best possible way to send this CVR along with the user/password at SSP.

Want to understand the way where this CVR can be passed in the header of the SSP login request which goes to SEAS for authentication. And SEAS being able to read that information.