- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
12-19-2024 11:01 AM
Hello everyone,
Has anyone had success using the Alero APIs for vendor invitations and group management in PCloud shared services? The documentation refers to Alero Swagger, but none of those APIs seem to work in ISPSS.
For instance, vendor invitation APIs use attributes in the payload, such as "provisioningType": "ProvisionedByAlero" and "provisioningGroups", which do not work in shared services.
Group management does not work at all, as the 'on-premises' Alero relied on LDAP groups, whereas Identity roles are now leveraged for this purpose.
This is a big roadblock when moving vendors from the 'old' Alero to Alero shared services.
Thank you.
12-26-2024 08:52 PM
Hi @Anderson Viotti
In this case you might have to opt for a workaround.
You can use the Remote Access portal for manual invitations while automating other workflows.
The provisioningType and provisioningGroups attributes may not work, but you can rely on the Identity APIs to manage roles and users.
Also in the shared services model, replace the concept of LDAP groups with Identity Roles and use the Identity Management API to manage roles.
12-29-2024 04:33 AM
Hi @Anderson Viotti
It seems that Malhar provided an answer to your question. Could you kindly let us know if this solution helped?
If so, please mark the answer as 'Select as Best' to assist other community members.
Thank you, Liad
01-02-2025 05:55 AM
Hello, inviting vendors via Identity itself does not work, as they use a different authentication method (Alero SAML > CyberArk Mobile app) and invitation needs to be sent by Alero.
It's interesting that when inviting vendors via UI and inspecting the logs, provisioningType changed from ProvisionedByAlero (Alero LDAP) to INTERNAL_LDAP (Alero Identity), and provisioningGroups changed to idaptiveRoles. I tried those new attributes via Alero Swagger, but it doesn't work. For instance, this is one of the errors:
Invalid Input: field value is invalid: INTERNAL_LDAP
Thanks.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!

