To begin using WIND for your application please send a request to
Please include the following information.
Service Name
A short string to be used as an identifier for your application.
Technical Contact e-mail Address
Someone knowledgeable about the technical aspects of your web application. The person must have a UNI and a Columbia email address.
Administrative Contact e-mail Address
A manager or other departmental contact (not the same as the technical contact). The person must have a UNI and a Columbia email address.
Brief description of Your Application
Just a sentence or two is fine.
UNI or Anonymous Identifiers
By default, validate requests will return a unique, persistent, anonymous identifier. You should indicate whether your application needs the user's UNI.
Since Columbia UNIs are considered academic records by the University, access is restricted to official Columbia services, or with the express permission of CUIT management. If you believe that your application requires UNIs, please explain why this is needed and describe how they will be used.
Response Format
Indicate whether you prefer XML- or plain text-formatted responses.
System information
Destination URI for the service.
Include one or more URIs where a user will be redirected after obtaining a ticket. Your service may have multiple URIs or a common substring for several different ones, but each registered destination must be unique (ignoring case) from every other destination used by every other service. Within a single service, it is possible to register multiple destinations that differ only in case.
440x50 GIF image to use as a logo.
Help link.
Help link label.
Should the Columbia links be present.
WIND can return affiliations data along with the success/failure message and the UNI. These can include information such as course enrollment information, CUNIX groups, alumni information, school affiliation, and faculty/officer/staff affiliation.
If you believe you need access to user affiliations, please keep in mind that this information is considered private directory information, and the university is legally obligated to protect its confidentiality. Permission to access affiliations must be approved by CUIT management. The request for such data should be as specific as possible and include an explanation of why you need it.
The Single Sign-On (SSO) system allows a user who has established a WIND session to log in to any SSO service without having to re-type his password. This is an opt-in feature, meaning that Single Sign-On only works between services that have it enabled. If a user logs in to one SSO service, then he can login to any other SSO service with a valid session cookie. Services which have not opted-in do not accept such session cookies, nor do logins to their service generate a valid cookie that could be used for SSO services.
If your service will accept proxied tickets, list the originating service(s) it will accept them from.