RESTful Web Service Connector capability test fails with unauthorized (401) error when using Basic authentication in RSA Governance & Lifecycle
Originally Published: 2024-06-04
Article Number
Applies To
- RSA Product Set: RSA Governance & Lifecycle
- RSA Version/Condition: 8.0
Issue
Upon creating a RESTful Web Service Connector for an endpoint (such as, Service Now) using Basic authentication type, the Test Connector Capability 'Update Account' fails with a 401 error. In Postman the same test works, returning a 200 OK success message.
Cause
Resolution
- RSA Governance & Lifecycle 8.0 P02
Related Articles
Generic REST Collector problems with Authentication (OAuth2, Bearer Token or Basic Authentication) in RSA Governance & Lif… 342Number of Views What are the steps to use a SID800 token with SecurID ready applications? 406Number of Views Unable to read a known contact list error while trying to test RSA Authentication Manager Integration Service (AMIS) using… 276Number of Views How to check local file system disk space usage for RSA Identity Governance & Lifecycle 1.33KNumber of Views Connecting to or querying the database using pgSQL in RSA Authentication Manager 8.x 1.79KNumber of Views
Trending Articles
AFX Server remains in a 'Not running' State, afx status shows 'timed out waiting for AFX applications to start' and mule_e… RSA Release Notes for RSA Authentication Manager 8.8 RSA Authentication Manager 8.7 SP1 Patch 1 Hotfix 1 Downloading RSA Authentication Manager license files or RSA Software token seed records RESTful Web Service Connector capability test fails with unauthorized (401) error when using Basic authentication in RSA G…
Don't see what you're looking for?