Facing "Request has been blocked by CORS policy: No 'Access-Control-Allow-Origin' header is present on the requested resource."

• Related Articles

• Facing CORS issue

  You need to add the domain from which you are calling your function in the Authorised Domains section present in Authentication Tab of the Catalyst Web Console. Kindly add your domain in the mentioned location and enable CORS and iFrame which will ...

• Authentication : Facing invalid client error

  This issue might occur if the client gets deleted in the API console. In order to resolve this issue, we would suggest you to navigate to Sign In Method under Authentication tab in Catalyst Console and then disable and enable the Sign In Using Zoho ...

• How do I redirect users upon logging in using Catalyst Authentication?

  You need to set the redirection URL in your application in your client-package.json file in order to redirect your application to that page after login. You can find the help documentation for the same here.

• How can I use a custom form for login, instead of the prebuilt catalyst.auth.signIn("your element id here....");

  As of now, it is not possible to have a custom Login UI and still use the Catalyst Authentication feature. The ideal implementation of your custom logic can be determined based on your use case/business logic.  

• Support for signup or sign-in from social accounts

  We do have support for authentication from other social accounts, email, etc on the roadmap. Please drop a note with your requirements