This chapter briefly introduces the Mobile and Social client SDKs. This chapter includes the following topics:
Section 7.2, "Introduction to Developing Mobile Services Applications"
Section 7.3, "Introduction to Developing Internet Identity Services Applications"
Before you start work on an application that will use the Oracle Access Management Mobile and Social service, you should read the "Understanding Mobile and Social" chapter in Oracle Fusion Middleware Administrator's Guide for Oracle Access Management. This Developer's Guide assumes that you understand Mobile and Social terminology and concepts.
In this guide the Mobile and Social client program (or client app) is the portion of code that you build into an application to utilize authentication, authorization, and user profile services on a remote server. Your application can be any application that uses HTTP. It does not have to be a mobile application.
Two Client SDKs—iOS and Java—are provided for building Identity security features into your applications and enabling you to use your existing Identity infrastructure for authentication, authorization, and directory-access services. The easiest way to get your app to interact with Mobile Services is to use one of the offered client SDKs.
Note:
If you are developing an application on a platform or device that cannot use the iOS or Java SDKs, you can write code to directly send Mobile and Social REST calls to the Mobile and Social server.
See Chapter 12, "Sending Mobile and Social REST Calls With cURL", which documents the Mobile and Social REST API.
If you use a Mobile Services SDK, you do not need to know the REST call syntax that the Mobile Services client uses to communicate with the Mobile and Social server.
The following table lists the features that each Mobile Services Client SDK is capable of.
Table 7-1 Features and Capabilities of the Java and iOS Mobile Services Client SDKs
| Feature | iOS | Java | Notes |
|---|---|---|---|
|
Build a mobile application that can acquire Client Registration Handle, User, and Access Tokens through a Mobile and Social Server |
✔ |
See Chapter 9, "Developing Mobile Services Applications with the iOS Client SDK." |
|
|
Build a desktop application that can acquire Client, User, and Access Tokens through a Mobile and Social Server |
✔ |
See Chapter 8, "Developing Mobile Services Applications with the Java Client SDK." |
|
|
Interact with a Directory server and implement User Profile Services |
✔ |
✔ |
See Chapter 9, "Developing Mobile Services Applications with the iOS Client SDK." See Chapter 8, "Developing Mobile Services Applications with the Java Client SDK." |
|
Create a mobile single sign-on (SSO) app |
✔ |
See Chapter 9, "Developing Mobile Services Applications with the iOS Client SDK." |
This section contains notes and information about building applications with User Profile Services. This information is not specific to any one SDK.
In general, LDAP attribute names are not case sensitive. When communicating with the Oracle Identity Governance Framework (IGF) APIs, however, LDAP attribute names are case sensitive.
Special characters should be replaced with their hex value equivalents in the search filter.
Note:
The WebLogic Server embedded LDAP server does not allow special characters to be included in the user name. User names are case sensitive and must be unique. Do not use commas, tabs, or any other characters in the following comma-separated list: < >, #, |, &, ?, ( ), { }
Developers who maintain Java-compliant Web applications can add Internet Identity Services functionality to their Web offering using the Mobile and Social Internet Identity Services SDK. This SDK is available for Java-powered Web applications only.
For information about how to use the SDK to integrate Internet Identity Services with a Java-powered Web application, see Chapter 10, "Developing Applications Using the Internet Identity Services Client SDK."
This Developer's Guide also includes information about how to add additional OpenID and OAuth Service Providers by implementing a Java interface. For information, see Section 11.2, "Create a new Identity Service Provider for Internet Identity Services".