A summary of available interfaces, their purpose and what can be obtained from them is:
Available CUD Interfaces
|Interface||Personal access||Server/service use||Authentication method preferred||Attributes available|
|CUD User Interface||Y||N||Webauth||CAS* plus special release|
|REST||N||Y||Kerberos||CAS* plus special release|
|SOAP query||N||Y||Kerberos||CAS* plus special release|
|SOAP push||N||Y||Various||CAS* plus special release|
|SQL Push||N||Y||As required for JDBC connection||CAS* plus special release|
|LDAP push||N||Y||LDAP simple bind over SSL/TLS||CAS* plus special release|
*CAS is the CUD Attribute Set; the default attributes available to all users of CUD
Choosing an interface
- If you're doing ad-hoc queries then you should use the CUD UI (User Interface).
- If you have a database which can be addressed remotely using a JDBC driver then you should strongly consider using the SQL push interface.
- If don't have a database, or prefer to download data as text files before loading them into the database, then you should look at the REST interface on the CUD Webservice.
- If you are using a packaged application that is able to use a remote webservice to import data then you should look at the CUD Webservice.
- If you are using a packaged application that is able to query a remote LDAP directory to import data then you should look at the LDAP interface.
The most commonly used interfaces are the CUD UI and REST. Details of how to apply for access to those are available in the CUD Access page.