Spoiler Spoiler Warning ▲▼
The Developer trial provides full-featured access to the same services that OpenText uses to power its SaaS products. In order to give you this access, we need to have a User ID that is aligned to our audit and traceability processes.
Why is there an “OpenText Connect" and a separate “Developer Trial" sign-up?
OT Connect is our customer ID system; it provides us with traceability, but it also provides a single ID to access the Developer forums as well as the Administrative console for the Developer trial. The good news is that if your company is a customer or partner of OpenText, you very likely already have an OT Connect account and can skip this step.
If you are new to OpenText, the OT Connect account that you create during the free trial will also be used when you become a customer. Furthermore, it is the same Administrative ID that you will use for technical support and for accessing our Core SaaS products. This means that if you are adding other products (e.g. Core Content or Core Case)then the sign-up and getting started process will be simplified.
The OT Connect login is a key piece of the personalization that we are bringing to the Developer experience. We have a separate sign-up for Developer ,at the moment, because the Token and API security IDs are tied to the tenant manager. As most of Developers will want a separate security this was the “V1” (version 1) way to create that separation. It also allows developers to use the same login to span multiple tenants and organizations which is key to the experience and starts giving us that one OpenText cloud identity.
