Verified Answers

If an answer to your question is correct, click on "Verify Answer" under the "More" button. The answer will now appear with a checkmark. Please be sure to always mark answers that resolve your issue as verified. Your fellow Community members will appreciate it! Learn more

  • State Verified Answer
  • Replies replies
    10
  • Answers answer
    1
  • Subscribers subscribers
    4
  • Views views
    1674
  • Users 0 members are here
  • +1 person also asked this people also asked this
  • Locked Locked
Related
Options
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

OpenText Connector Authentication Examples

Phil Cox
 

All

I'm looking for an example of Authentication when using OpenText Connector.  When I use REST API into Content Server for authentication I get back OTCSTicket that I use in header.  Any examples of how to configure the OpenText connector are welcome.

Many thanks

Parents

  • Verified Answer

    +1  

    The OpenText connector has configuration options for ‘Username’ and ‘Password’. These are used with the ‘api/v1/auth’ endpoint to retrieve a ticket that is used to populate the ‘OTCSTicket’ header for further requests. An example connector configuration task section would be as follows:

    [MyTask1]

    OpenTextApiUrl=my.contentserver.instance/.../cs

    Username=MyUser

    Password=P@ssword!

Reply

  • Verified Answer

    +1  

    The OpenText connector has configuration options for ‘Username’ and ‘Password’. These are used with the ‘api/v1/auth’ endpoint to retrieve a ticket that is used to populate the ‘OTCSTicket’ header for further requests. An example connector configuration task section would be as follows:

    [MyTask1]

    OpenTextApiUrl=my.contentserver.instance/.../cs

    Username=MyUser

    Password=P@ssword!

Children

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.