---
title: "Required Information for SSO Integration Requests"
canonical: "https://kb.uconn.edu/space/IKB/28612362251/Required%20Information%20for%20SSO%20Integration%20Requests"
format: markdown
---
Please include as much of the following information when submitting a request for application integration with Microsoft Entra. Providing complete information helps the IAM team review the request and begin planning the integration.

## Application Information

### Application Name  

Enter the full name of the application.

### **Vendor / Provider**  

Enter the name of the vendor, provider, or hosting organization.

### **Application URL (login URL)**  

Provide the primary application or login page URL.

### **Environment**  

Indicate whether the request is for:

- Production
- Test
- Both

### **Application Purpose**  

Briefly describe what the application does and who uses it.

## Technical Contact Information

### **Primary Technical Contact**

Provide the name and email address of the primary technical or administrative contact.

### **Vendor Support Contact**  

Provide the vendor support or technical contact, if different.

### **Vendor Engaged**  

Has the vendor been contacted and made aware of this SSO request?  

- Yes/No

## SSO / Federation Details

### **Supported SSO Protocol(s)**

List the supported protocol(s), such as:

- SAML 2.0
- OpenID Connect (OIDC)
- OAuth
- CAS

#### If SAML

- **Metadata URL**    
Provide the metadata URL, if available.
- **Entity ID / Audience URI**    
Provide the Entity ID or Audience URI, if known.
- **Assertion Consumer Service (ACS) URL / Reply URL**    
Provide the ACS or Reply URL.
- **Sign-on URL**    
Provide the sign-on URL, if different from the ACS URL.
- **Logout URL**    
Provide the logout URL, if supported.

#### If OIDC

- **Redirect URI**    
Provide the redirect URI.

## Attributes and User Identification

### **Unique Identifier**

What attribute does the application use as the unique user identifier?    
Examples:

- NetID (Preferred)
- Email
- Other

### **Required User Attributes**

List any required attributes, if known. Examples:

- First name
- Last name
- Email
- Affiliation

### **Custom Attributes or Roles**

Does the application require any custom attributes, claims, or roles?

## Access and Provisioning

### **Who Needs Access?**

Describe the intended user population. Examples:

- Specific department
- All faculty and staff
- All users
- Students

### **Automatic User Provisioning Required?**  

- Yes/No

### **Access Restrictions**

Should access be restricted based on:

- Role
- Affiliation
- Group

### **Provisioning Method**

If provisioning is required, does the application support SCIM or another provisioning method?