Table of Contents

Search

  1. Preface
  2. Introduction
  3. IDD Concepts
  4. Implementation Process
  5. IDD Configuration Manager
  6. Manual IDD Configuration
  7. IDD Global Properties
  8. Appendix A: Sizing and Platform Requirements
  9. Appendix B: Application Components
  10. Appendix C: IDD Security Configuration
  11. Appendix D: Data Security
  12. Appendix E: Example Role-Based Security Configuration
  13. Appendix F: Data Masking
  14. Appendix G: Siperian BPM Workflow Engine
  15. Appendix H: Locale Codes
  16. Appendix I: Troubleshooting
  17. Appendix J: Glossary

Data Director Implementation Guide

Data Director Implementation Guide

Other Considerations

Other Considerations

When planning security for your IDD application, consider the following issues:
  • For IDD to access Informatica MDM Hub resources, the resources must be configured as SECURE (not private) in the Secure Resources tool in the Hub Console.
  • SAM is configured on a per-ORS basis. When you add IDD users, you need to set the IDD schema as the default database for these users.
  • In the Data workspace, IDD users typically will not see explicit error messages for insufficient privileges. For example, a certain resource might simply be hidden from the user because they are not configured to access it. When testing your security configuration, refer to the server log for debugging information.
  • In an entity workspace, IDD displays all resources regardless of user role. When users perform actions for which they do not have the required security permission, IDD displays error messages.
  • The security configuration is stored in two places: in the Hub Server cache and the IDD cache. There is a slight lag time (1 minute) to synchronize changes. In a development environment, you can restart the server to refresh the cache.

0 COMMENTS

We’d like to hear from you!