About this Manual
The focus of this guide is to:
- Introduce the different challenges that the RadiantOne platform addresses.
- Introduce ways to architect the solution while taking into account specific security requirements for authentication and authorization.
This guide is primarily for architects in charge of designing the solution to match the use case at hand. Although this document would be a valuable introduction for a RadiantOne administrator, it does not describe any step-by-step configuration details. This type of information is detailed in the RadiantOne System Administration Guide and RadiantOne Namespace Configuration Guide. References to other relevant RadiantOne documentation are included throughout this guide.
This manual is written with the assumption that the reader is familiar with the following LDAP and relational database terminology and concepts:
- General knowledge regarding the structure of a directory information tree (DIT)
How the Manual is Organized
This guide is broken down into the following chapters:
The first chapter of this guide describes the RadiantOne identity source integration capabilities. In particular, it covers the different layers involved in a directory design and how each work alongside one another.
This chapter develops the concept of “identity union” in addition to concepts for handling issues such as authentication and authorization when facing an identity aggregation/integration challenge.
Virtual View Design
This chapter focuses on the design considerations and options when building a view for addressing authentication, authorization and security.
Common Use Cases
This chapter covers frequently seen usages for the RadiantOne platform.
Getting Started with RadiantOne
This chapter offers advice for the best ways to get started using RadiantOne. This includes an introduction to the two different Control Panels along with descriptions of which namespace configuration approach to use and what the best tool/wizard is to get you started.
The final chapter focuses on how to use persistent caching to achive performance expectations.
Technical support can be reached using email or our support website:
E-mail: [email protected]