mrtimp
commented
3 years ago Ahh ha, found this: https://docs.solus.io/en-US/latest/billing/postpaid-billing/custom-billing-integration.3/#step-9-configure-automatic-logging-in-to-solusio for anyone wanting to do SSO.
Hi there,
I notice that #8 was closed and understand the design implications to this based on the use case but I wanted to propose the current situation that we have.
We are not planning to integrate with SolusIO using either of the WHMCS modules as we have a bespoke billing requirement.
In WHMCS we are planning to allow customers to purchase a single product which essentially is a $0 service that we can use to then associate the client in WHMCS with the user in SolusIO. We would then like to have a very simple client area that displays a list of resources that the customer has in SolusIO and an option for the customer to SSO from WHMCS into the SolusIO customer area (we would source this information from the various resources API's). WE expect the WHMCS client area to be read-only and intend for customers to manage all of their SolusIO resources in the SolusIO client area. We would like SSO to improve the customer experience of not having to remember multiple credentials and that the simply log into WHMCS and can then SSO from there to SolusIO/Plesk and other services we sell.
It would be handy if you could optionally use the /api/v1/users/{id}/tokens API endpoint to create a one-time user token that you could then use via /api/v1/login as a bearer token to authenticate the user into the SolusIO client area.
You wouldn't have to incorporate the proposed SSO functionality into the existing WHMCS modules but it would allow people with different requirements the ability to handle SSO to meet their requirements.