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

Provide a Simplified Login Options

There are business scenarios wherein a Simplified Login option would be preferable to a full User Login. An example would be, allow a user to simply login using OTP which will authorize them to perform X actions on the Application and then the Application can perform Step-Up Authentication if the user needs to perform some action outside of the original authorization.

  • Guest
  • Jan 2 2020
  • Planned for future release
  • Guest commented
    7 Jan, 2020 04:01pm

    I can see both scenarios. Our initial priority would be to allow Applications to offer a Simplified Login (e.g., User does not have an Account, User is prompted for Email Address, OTP is sent to user's Email Address, User is granted basic access to Application). If the user then wants to take some further action (e.g., I want to purchase a service from this Application), then application would prompt user to create a full Account.


    The secondary priority would be allowing the user, or Application on the user's behalf, to only be able to perform certain actions based on how the user authenticated. The actions permitted would be controlled via a Policy set per Application. Example: User logs in with Simplified Login, Application can only perform READ actions on user's behalf whereas User logs in with MFA, Application can now perform WRITE actions on user's behalf.

  • Guest commented
    7 Jan, 2020 12:54pm

    Hello! Thanks for your idea.

    Looking at the request, are you wanting to be able to set fine grained permissions on certain CI actions based on how the user logged in? Or are you referring to the application you have written that needs to consume how the user logs in and then reacts to that?


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.