Found this awhile back. It helped me and I will try and outline what I did outside of these steps/instructions:
Description
When unauthenticated users try to submit a public catalog item in Service Portal, a 400 Bad Request error occurs and they are unable to submit. This issue is due to AngularProcessor authentication restrictions.
Steps
Catalog Item Configuration
- The catalog item(s) intended for unauthenticated submission must have a 'User Criteria' that allows access to the public role
- The variables must allow 'Create' permissions to the public role
Limitation
Adding attachments is not supported as a public user so as a best practice, use Portal settings to hide the attachment section fro public catalog items
- Create your record producer or catalog item and make it public
- Portal Settings (tab) – Hide Attachment, and Hide ‘Add to Wish List’ (checked)
- Script – (Record Producer) ‘producer.portal_redirect = ‘any_redirect_page’
- Available for (tab) – Create or add ‘User Criteria’ record
Note: Role should be ‘public, snc_external’
- Variables – make sure the write, read, and create roles are ‘publi’
Note: Reference and List Collector variables must allow ‘Read’ access to that table content
- Create a Portal (fill in as needed)
- url suffix
- homepage
- theme
Note: you can make the (sc_cat_item) page public and not create a custom portal or pages (I create a custom page so I could leave ‘sc_cat_item’ page as is)
2. Make any widgets associated with your page or the sc_cat_item page public as well
3. Open the item in a incognito window [/sp?id=sc_cat_item&sys_id= 0c35909cb14156bc4bcbe33938409]
Note: add your custom page name in the url if you created a custom page. Although the catalog item is public, it will not allow you to submit the item
Workaround
To allow unauthenticated users access to catalog items, the following needs to be done (on instances running New York Patch 9, Orlando Patch 4 or higher):
Widget/Page Configuration
The following Service Portal Page(s) and Widget(s) must be configured to allow access to the public role:
- Catalog Item Service Portal Page (sc_cat_item)
- SC Catalog Item Widget
- SC Order Guide Widget
- Catalog Checkout Widget (if two step checkout has been enabled)
- SC Order Status page and the Order Status widget
API Configuration
All the REST APIs used on the above mentioned widgets/pages must be configured to allow unauthenticated access by unchecking the `Requires Authentication` field in the REST API configuration. This includes the following API(s):
- Buy Item
- Submit a Record Producer
- Validate Variable Regex (In case the item consists of a variable which requires Regex Validation)
- Checkout Order Guide
- Variable display value
- Check requested for delegation on item. (Paris onwards)
If these REST APIs are configured to require authentication, they throw a `403 Unauthorized error` when accessed by a public user
Customers may need to reach out to the ServiceNow Support for making these API and Widget configurations
Catalog Item Configuration
- The catalog item(s) intended for unauthenticated submission must have a User Criteria that allows access to the public role
- The variables must allow Create permissions to the public role
Limitation
- Adding attachments is not supported as a public user so as a best practice, use Portal Settings to hide the attachment section for public catalog items.
- At present we do not support public Multirow Variable Set.
Related Problem: PRB854474
if you see the article it has mentioned to update the api method field "Requires Authentication" .
go to the scripted Rest API >> search for "Service Catalog API" >> you will see list of method (Resources tab), so make the changes to those method field "Requires Authentication"
Screenshot for an example for buy Item method.
Hi @Magnum1 ,
I had added the public role access table and table.*, but reference field still don't have records, do you have any ideal? Thanks.
