Manage ID provider users with IBM Cloud
This documentation is relevant to the new IBM Quantum® Platform. If you need the previous version, return to the IBM Quantum Platform Classic documentation.
App ID creates an ID provider so you can add users directly in App ID or connect to other external ID providers. This guide gives an overview of how to set up your ID provider to work with IBM Cloud® users and how users will access the environment. You can also view the full App ID documentation.
To manage users in a different way, follow the instructions in one of these topics:
Steps
Follow these high-level steps to set up your environment:
-
Configure the ID provider.
- Use the Cloud Directory capability to add users to the ID provider. Open the IBM Cloud resource list, search for your App ID instance and click its name to edit its details.
- Refer to the App ID documentation for instructions how to integrate other ID providers into App ID.
-
Integrate the App ID instance as the ID provider for the administrator's account on the Identity Providers page. See Managing authentication for full details.
After enabling enable the ID provider, default IdP URL is shown. Share this URL with users when they need to log in.
-
Add users. When you use App ID as ID provider with the Cloud directory, you can create users in the Cloud user interface from the resource list.
-
Create or modify users' project assignments from the IAM user page.
If you don't see the user that you want to manage, verify that they logged in to IBM Cloud at least once.
-
Add or modify users' access groups from the IAM user page.
User flow
-
A user is sent the ID provider URL for the IBM Cloud account. They use this URL and the login information to access the system. The user should change their password after they log on.
NoteThe administrator can always go to Manage → Access (IAM) → Identity providers to look up the ID provider URL.
-
The user create an API key from (Manage → Access (IAM) → API keys).
-
For further information, users can review Install Qiskit.
Example scenario
This example creates the following setup:
- There are two projects,
ml
andfinance
.- The
ml
project needs access to the service instancesQR-ml
andQR-common
. - The
finance
project should have access to the service instancesQR-finance
andQR-common
.
- The
- There are three users:
- Fatima needs access to the
ml
project. - Ravi needs access to the
finance
project. - Amyra needs access to both projects.
- Fatima needs access to the
- It uses access groups without resource groups.
- Users are defined in IBM Cloud but project assignments are done in an App ID instance.
- Users should be able to delete jobs.
The steps to implement this setup are:
-
The Cloud administrator creates an App ID instance and ensures that it is linked in the Cloud administrator's account. The administrator notes the ID provider URL to share it with users.
-
The Cloud administrator creates three service instances:
QR-ml
,QR finance
, andQR-common
. -
The Cloud administrator creates a custom rule that includes the
quantum-computing.job.delete
action. -
The Cloud administrator creates two access groups:
- The
ml
access group can accessQR-ml
andQR-common
. This access group needs a dynamic rule for the App ID IDP that accepts users whoseproject
attribute containsml
. - The
finance
access group can accessQR-finance
andQR-common
. This access group needs a dynamic rule for the App ID IDP that accepts users whoseproject
attribute containsfinance
.
- The
-
The ID provider administrator defines the three users in the IBM Cloud user interface.
-
Users log in at least once.
-
The cloud administrator assigns access by adding users to the access groups that give them access to the projects:
- Fatima is given access to the
ml
project. - Ravi is given access to the
finance
project. - Amyra is given access to the
ml
andfinanace
projects.
- Fatima is given access to the
-
Users can log in through the ID provider URL, create API keys, and work with their projects' service instances.
Next steps
- See IBM Cloud SAML Federation Guide for more information.
- Refer to the full App ID documentation.