Using the REST API in AM/OpenAM

This book provides information on using the REST API in AM/OpenAM and includes known issues (including solutions).

Printer friendly view

Table of Contents

  • 1 How do I update REST API calls after upgrading to a newer version of AM/OpenAM?
  • 2 How do I avoid common issues with REST calls in AM/OpenAM (All versions)?
  • 3 How do I retrieve user attributes from a session using the REST API in AM (All versions) and OpenAM 13.5?
  • 4 How do I update LDAP user attributes using the REST API in AM/OpenAM (All versions)?
  • 5 How do I assign password policies to a user when creating the user via the REST API in AM/OpenAM (All versions)?
  • 6 How do I unlock a user's account using the REST API in AM/OpenAM (All versions)?
  • 7 How do I change a user's password using the REST API in AM/OpenAM (All versions)?
  • 8 How do I force REST API responses to always use lower case for attribute names in AM/OpenAM (All versions)?
  • 9 FAQ: REST API in AM/OpenAM
  • 10 REST - for the rest of us
  • 11 Known Issues
    • 11.1 400 response when adding or updating resources via REST or Amster when the resource name contains forward slashes in AM/OpenAM (All versions)
    • 11.2 400 response with json/users endpoint in AM/OpenAM (All versions) if username contains forward slash
    • 11.3 Minimum password length is 8 error in AM (All versions) when updating identities using the REST API
    • 11.4 REST API calls fail after upgrading to OpenAM 13.x
    • 11.5 Unable to login to OpenAM 13.x console or access REST API after changing the Federation Signing Key
    • 11.6 Authentication fails in OpenAM 13 if username or password has non-English characters in a REST call
    • 11.7 Policy import fails in OpenAM 13.0 with Invalid resource type null message