IBM Security Verify

Shape the future of IBM Security Verify

We invite you to shape the future of IBM, including the product roadmap, by submitting ideas that matter to you the most.

Here's how it works:

Post your ideas

Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you,

  1. Post an idea

  2. Upvote ideas that matter most to you

  3. Get feedback from the IBM team to refine your idea

Submit a private idea

If you have confidential information or customer data to share with your idea, then - DO NOT submit using the link below, instead - please open a private feature request.

And finally - if its an issue with expected behaviour, a product defect or a support need, open a Support Case

Approval workflow during User (Self-)Registration

Today, Verify SaaS provides different ways for creating new user entries in the Cloud Directory (Admin GUI, Self-Registration User Experience, REST API). Unfortunately, there is no Approval Workflow which can be triggered from any of the Create User methods.

We should enhance Verify SaaS by adding a Approval Workflow feature to the Create User operation. The minimum requirement would be to support a optional one-step Approval activity in case of End User Self-Registration. This would be a important security and stability feature since it would allow to mitigate the risk of Denial Of Service attacks and to increase the quality of end user data.

If an Approval workflow could be triggered for any Create User event, regardless whether it has been created by Admin GUI, self-registration or API, then this feature would be even more valuable.

  • Guest
  • Apr 7 2022
  • Needs more information
  • Admin
    PHILIP NYE commented
    17 May 03:37am

    We appreciate the requirement to do it as part of a self registration, can you elaborate on the requirement for administration or API flows?


By clicking the "Post Comment" or "Submit Idea" button, you are agreeing to the IBM Ideas Portal Terms of Use.
Do not place IBM confidential, company confidential, or personal information into any field.