In this chapter we have extensively covered most of the supported REST interfaces of OpenSSO identity web services. It does have decent support for the operations that are typically consumed by the client-side programs. Nevertheless, as you might have noticed, none of the administrative or monitoring interfaces are exposed through the REST interfaces intentionally. This makes sense as the administrative activities can be carried out using the console. Any operation that is performed on identities via the REST interfaces will be reflected on all of the configured data stores in the realm. When these interfaces are invoked using a client browser, the customer must make sure that the values are encoded appropriately. There is a nice blog entry on OpenAM REST operations at http://blogs.forgerock.org/petermajor/2010/05/using-the-rest-api-for-identity-management/. It includes some tips and some other comprehensive help as well.

So far we have discussed most of the core services provided by the OpenSSO, but you might be wondering, "What if my server crashed? What if my configuration is corrupted or lost? How do I recover from the crash?" next chapter is the answer to your questions. In the succeeding chapter we are to going focus on backup and recovery process at length. Another interesting topic that is waiting to be discovered by you is the auditing feature. Auditing forms the third A in the AAA (Authentication, Authorization, and Audit) which is a critical piece in access management. In the next chapter, you can find various auditing features and ways to configure them in OpenSSO.