Currently, in MDM 7.1, there is no Single Sign-on (SSO) support. The client applications willing to connect to MDM would always need to provide the MDM usernames and passwords to log on to the MDM system and access the repositories.

However, there is a trusted connection concept in MDM 7.1 that allows MDM APIs from trusted systems to connect to the MDM server or repository without supplying the password. This way the specific system in the landscape is trusted by the MDM server.

MDM APIs are available for:

MDM APIs for ABAP use an extended trusted connection concept by always passing the logged on AS ABAP username (sy-uname) to the MDM server. The ABAP username (sy-uname) must be available in the repository Users table, so that the MDM login is successful through the ABAP API. The trusted connection is then established between the MDM server and the AS ABAP server.

In case of COM/Java/.NET trusted connections, you can simply pass the existing MDM username...