---
title: "Request NetID database user for direct Oracle access"
canonical: "https://kb.uconn.edu/space/DMRA/28572057601/Request%20NetID%20database%20user%20for%20direct%20Oracle%20access"
format: markdown
---
# <u>**SAILPOINT - GENERATE A REQUEST FOR A  NEW ORACLE DATABASE USER**</u>

 

1. This link will take you to the logon screen if you are not already logged in.

[https://uconn.identitynow.com/ui/d/request-center/requesting-for](https://uconn.identitynow.com/ui/d/request-center/requesting-for)

![image-20260109-184209.png](media://47092c93-ad96-49f8-a6d8-3172d84cc088)

 

2. After the login, click on the request center and choose ‘Request for Yourself’ or ‘Request for Others’ (Request for Others will be used most often).

![image-20260109-185625.png](media://1108a073-9d43-4a11-b80e-28e85dc7093e)


3. If you select ‘Request for Others’ from the drop-down, select who the request is for.

      NOTE: You can choose one or many people for the request.

![image-20260109-185946.png](media://1bc9f9cd-72cc-488f-b037-5665a831be32)


4. For this example, I have only chosen one person: Fabrice Njeh.  Click ‘Request for These Identities’.

![image-20260109-190400.png](media://5bd721d1-2f7d-4952-b0c7-023c2d0936f2)


5. Select your desired Database.  In this example, ‘Oracle DB - aewebp.uits.uconn.edu’ is selected.

![image-20260110-134050.png](media://535437fb-84ea-4949-a7bf-c430ff6c0e41)


6. Select the access you wish to request

![image-20260110-134402.png](media://5d411357-3f5b-4272-b456-1b0145ba74c2)


7. For this example, ‘Access Profile: Provision an Account on the Database with the CONNECT privilege’ is selected, then click ‘Save 1 Selection’ at the bottom.

![image-20260110-140108.png](media://92a12db1-8320-4c9d-86f7-88049fa193fc)


8. Click ‘Review Request’.

![image-20260110-141045.png](media://bb7da5a5-0a98-4a63-8ce2-3ec891667716)


9. From this screen, you can set a time limit (expiration) for the userid and/or add comments by selecting ‘Edit 1 Access Profile.’

![image-20260110-142026.png](media://016faccf-8d94-44ab-84da-54e8ce8d1adf)

 

10. When the screen to the right opens up, an expiration date can be entered if desired.

![image-20260110-142447.png](media://544dc4a1-e45a-4699-85ea-ea8c10279de1)

 

 11. Click ‘Save’.

![image-20260110-152710.png](media://dfe021b0-3eca-4cab-8d6d-ad2ab2d674ae)

 

12. Click ‘Submit Request'.

![image-20260110-153019.png](media://88f5ac08-be47-432d-8401-b342e769fb43)


13. If the submission was successful, the following message should appear:

![image-20260110-153541.png](media://4299ea86-a39f-48e6-af9a-bdd722641986)


14. The person making the request receives an email verifying submission:

![image-20260110-154041.png](media://98568d0e-52b4-4406-89f4-bae8414f1f44)


15. Behind the scenes, a Jira Ticket is generated and assigned to the DBA Group to complete the required SailPoint authorization request.  The initial User ID created by the SailPoint part of the process only grants connect privileges. The Jira portion is necessary to add any further privileges to the new account, such as select, update, or delete.  The email is sent to the database owner to obtain approval.
  Example of Jira Ticket Generated:
  
16. Lastly, log in to the JIRA ticket system and complete the authorization request.  This includes setting a unique password and securely sending it separately to the user ID owner.  Since SailPoint only creates the user ID with minimal privileges, the Jira ticket serves as the point of communication to determine which privileges the user is requesting and will actually be granted.


17. Completed view of the ticket in Jira:

![image-20260113-132501.png](media://f3adbf47-aed0-42af-a150-2dab9ba6cf67)


**APPENDIX**

SailPoint constantly monitors for changes to accounts.  If there is a department change or an employee has left the university, SailPoint will generate an email to the Database owner and create a Jira ticket to confirm access is still needed or remove/drop the user account.