Hi Dirk,
I do believe that my arguments cover the logic taken by ServiceNow for the Vendor Assessment Portal. Not everything should be centralised, not when it's for external contact that can't log into your instance main interface or anywhere on your network.
I believe that when the KB article specify "implement a portal (like Vendor Portal)" they are not speaking of the Vendor Assessment Portal itself, but some custom portal that compare to the Vendor Assessment Portal.
The other Community post refer to an older version of the solution. Jakarta was the first release of Vendor Risk Management. I did look, but found nothing regarding this point in the official Release notes.
There was also not a single mention of SSO in the (London) Vendor Risk Management Implementation course and exam that I passed.
Should you choose to force SSO to third party vendors, what would be the process to create users, update password and disable users? Who would be in charge? What would be the communication channel used? Will the vendor risk assessors have to interact with the team in charge of the SSO for every contacts? To automatise that process, I expect that you would have to hide several of the out-of-the-box widgets in the Vendor Assessment Portal and remplace them by your own custom versions.
Going against the platform's logic implies implementation costs, and may have unexpected maintenance costs in the future.
Of course, should I be mistaken, please share your experience here. ^_^
∴
Best regards from Switzerland
Shiva :¬,
If this reply assisted you, please consider marking it 👍Helpful.
This enables other customers to learn from this thread.
