SSPR User Discussions

Home

Rename "login hint" sent as optional parameter with oauth authorization request

Alex McHugh Super User

Super User

2 months ago

SSPR has a feature that allows us to use the macro syntax and send extra info as part of an auth redirect to remote OAUTH2 server.

However, it does NOT allow us to rename the prefix... it is always "&login_hint=<whatever macro expanded as>"

I would like to have this string say something else. Anyone know how to achieve this in a vaguely supported manner?

Suggested Answer

0 Liam O Dowd 1 month ago

Hi Alex,

I have discussed this internally could you open a case with support so we can look into this further.

Regards,

Liam O’Dowd
Global Technical Support

Micro Focus, an OpenText Company

For urgent access to our support teams please use our Chat Service or Phone as detailed below:
Chat: https://portal.microfocus.com
Phone: https://support.microfocus.com/contact/swgrp.html

For comments on our support service please contact my manager: Daniel Lopez (dlopez2@opentext.com)
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Reject Answer

Cancel
0 Alex McHugh 1 month ago in reply to Liam O Dowd

I think I will raise this as an idea / feature request. It is not strictly required for the project I am working on now.
Cancel
Vote Up 0 Vote Down

Sign in to reply

Verify Answer

Cancel
0 Alex McHugh 1 month ago in reply to Alex McHugh

I have now raised this as an idea, (+) More flexibility regarding the optional parameters sent in an authorization request when using the OAuth integration. - SSPR Idea Exchange - OpenText NetIQ Self Service Password Reset (microfocus.com)

Vote for it if you think it is a worthwhile addition to the product.
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.