---
title: "Identity & Access Services for Application Owners"
canonical: "https://kb.uconn.edu/space/IKB/27866660925/Identity%20%26%20Access%20Services%20for%20Application%20Owners"
format: markdown
---
## Overview

The Identity & Access Certification Service is now available for application owners at UConn. This service helps ensure that the right people have the right access to your applications—improving security, compliance, and operational efficiency.

SailPoint Identity Security Cloud allows us to centralize access visibility, manage entitlements, and automate periodic user access reviews (certifications) for applications across campus.

 

As part of this service, you will gain:

- **Access Review Campaigns:** Automate user access reviews (quarterly, annually, etc.)
- **Role & Entitlement Modeling:** Define what roles exist in your app and what access they grant
- **Delegated Access Approvals:** Approve/deny access requests via a self-service portal
- **Access Reporting:** Gain real-time visibility into who has access to your app and why
- **Audit & Compliance Support:** Streamline audits and reduce risk of overprovisioning

 

**What We Need from Application Owners**

To onboard your application into SailPoint and enable user access reviews, we’ll need a few key details from you:

1. **Authentication Method**

*How do users log in to your application?*

Please tell us:

- Is authentication handled internally by your app or externally (e.g., SSO, SAML, CAS, LDAP)?
- If external: Which identity provider (IdP) is used?
- If SSO is used, is the app integrated with the university’s central authentication service?

2. **Authorization Model**

*How does your app decide what users can do once they're logged in?*

Please provide:

- How access is granted—manually by admins, automatically based on attributes, or integrated with another system
- How access is revoked or changed

3. **User Account Data**

*We need to know how to connect SailPoint to your user data.*

Please confirm:

- Where user accounts are stored (e.g., internal DB, AD, LDAP, external directory)
- Whether there’s an API, database, or flat file feed available for reading user access data
- Whether we can write back (provision/deprovision) or only read access data (view-only)

## Contact us at [iam@uconn.edu](mailto:iam@uconn.edu)