Siebel REST API Services Cannot Get Information For Repository Objects With Names Starting with 'Config' - Errors Retuned SBL-SEC-10019 and SBL-DAT-00580 - 'The username cannot be empty. Please select a username'
(Doc ID 2766666.1)
Last updated on MAY 21, 2021
Applies to:Siebel CRM - Version 20.4 and later
Information in this document applies to any platform.
On a Development / Test environment, it was found that Siebel REST API requests cannot get information returned for some various standard Siebel Repository objects.
When trying to query for some web templates for instance using Siebel REST API an error is returned that username and password are not passed to the server.
But authentication data was present in the request - and for some other web templates, the same query works perfectly.
If tested using Postman for example, one would also see - HTTP 401 'Not authorized' response returned for those failing requests.
Steps to replicate the issue:
1. Using Postman or curl issue the REST API requests for various standard Repository Objects similar to above ones
2. See the requests completing fine for most of those objects
3. But for some of those - having names starting with 'Config*', see the error returned instead.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document