Service Virtualization 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 reply
1
Answers answer
1
Subscribers subscribers
5
Views views
471
Users 0 members are here
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

How to handle the authorization token in SCA

Swapnali Patil over 1 year ago

We need to handle the dynamic values of Basic Authentication token sent along with request. We need to pass through the token value in SCA.

If the authorization token value is not supplied, we will encounter the "Authentication Denied" error message.

Top Replies

Jakub over 1 year ago +1 suggested

if the username/password is static, you can provide it in the Credential Store. You will need to bind the credential to SCA through the identity name field in following form: SCA:<name of called activity…

Suggested Answer

0 Jakub over 1 year ago

if the username/password is static, you can provide it in the Credential Store. You will need to bind the credential to SCA through the identity name field in following form:

SCA:<name of called activity>

See:

https://admhelp.microfocus.com/sv/en/2022-2022-r2/Help/Content/UG/t_call_external_services.htm

https://admhelp.microfocus.com/sv/en/2022-2022-r2/Help/Content/UG/ui_edit_credential_store_dbox.htm

If it is dynamic, you can try to add Authorization header and populate it manually via scripting or data rule or you can use Protocol Hook. The header structure is described for example here: en.wikipedia.org/.../Basic_access_authentication
Cancel
Vote Up +1 Vote Down

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.