Operations Orchestration User Discussions

Home

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 Suggested Answer
Replies replies
4
Answers answer
1
Subscribers subscribers
175
Views views
579
Users 0 members are here

Related

Options

Execute OO Flow via Rest (OO Containerized)

Noah Föcking 7 months ago

Hi all,

is there a possibility to execute an OO Flow via REST API for OO Containarized?

If so, how does it work?

We tried it with an Admin OO User which has the permission to execute flows but via API we get a HTTP Status Code 403 Forbidden.

Best regards,

Noah

Tags:

REST Call

OO

containers

Operations Orchestration

Top Replies

Suggested Answer

0 Kumitikka 7 months ago

I have no experience on containerized OO but sounds like you are missing the CSRF token from your request. Refer to this https://docs.microfocus.com/doc/Operations_Orchestration/24.1/CSRFProtectionOO

In a nut shell run first a GET query to fetch the CSRF token and include it in the header of your POST call.

Although I am an OpenText employee, I am speaking for myself and not for OpenText.
If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel
0 Noah Föcking 7 months ago in reply to Kumitikka

Many thanks for the tip.

The POST does work if you enter a CSRF token, but so far I have not been able to get the token from OO somehow. I just cut it out of the browser context.

Unfortunately, it does not work as in the documentation in OO Containerized.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Kumitikka 7 months ago in reply to Noah Föcking

I found the Containerized OO REST API doc from here https://docs.microfocus.com/api/Operations_Orchestration/2023.05/OO%20Central%20API/v1 .

Authentication looks different to Classic with token based authentication retrieved from /idm/v3.0/tokens and using as value for X-Auth-Token with POST requests. Did you already try this?

Although I am an OpenText employee, I am speaking for myself and not for OpenText.
If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button
Cancel
Vote Up +1 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Noah Föcking 7 months ago in reply to Kumitikka

The API documentation helped me a lot. I am now further along and can make all API calls against OO Containerized.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel

Resources

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.