Installation Guides › Implementation Guide › Architectural Considerations › Implementation Considerations › Identify User Stores

Identify User Stores

SOA Security Manager can authenticate and authorize users through one or more connections to existing user stores in your enterprise network. After you identify the web services to secure, consider the following questions:

• Do the web services use a centralized user store or use separate user stores for authentication?
• If the web services use separate stores, does this project include a task to centralize the user identities into a single store?
• Do the web services use the same store to authenticate and authorize users? Or is a separate store or stores used for authorization?

Identifying the stores each web service uses helps you to:

• Identify the user store connections a SOA Security Manager Administrator must configure in a SOA Security Manager policy domain to protect the resource.

  Note: For more information about configuring user store connections within a domain, see the [set the co variable for your book].

• Determine if your environment requires the SOA Security Manager directory mapping feature. By default, SOA Security Manager assumes that users are authenticated and authorized against the same user store or stores. However, you can configure a SOA Security Manager policy domain to authenticate against one or more stores and authorize against others.

  Note: For more information about directory mapping, see the [set the co variable for your book].

When gathering information about each web service, use a table similar to the following to organize information:

More information:

Identify the Web Services to Secure