Calling all Racers for the Alteryx Grand Prix! It's time to rev your engines and race to the stage at Inspire! Sign up here.
3/24/2023: We are aware of the missing content issue and are currently looking into the matter. We appreciate your patience as we get this resolved.

Alteryx Server Knowledge Base

Definitive answers from Server experts.

Page Not Found after login to gallery when using SAML authentication


Error: “Page Not Found” or "403 Forbidden"


Environment Details

This article aims to provide a solution for account lockouts preventing users from successfully logging in.
  • Alteryx Server
    • All Version
  • SAML Authentication

Unable to log in to the gallery when using SAML authentication. User/Admin getting “Page Not Found” or "403 Forbidden" after clicking on "Sign in" button and completing the SAML login process.

Error message observed in gallery logs
ERROR,31,AlteryxServerHost,ErrorHandler,HandleError,,,,,,,,,,Exception caught by ErrorHandler and marshaled to client,"Alteryx.Server.Common.Exceptions.ForbiddenException: Access denied.->   at Alteryx.Server.Models.Presenters.UserPresenter.AddUser(User user)->   at SyncInvokeAddUser(Object , Object[] , Object[] )
  • "Page Not Found" error message on the Gallery UI
  • "403 Forbidden" in the web browser
  • "One or more errors occurred." in HAR trace



“Page Not Found” or "403 Forbidden" after clicking on the "sign in" button when SAML authentication is often caused when new users are not allowed to register in Gallery. While using windows authentication is enabled by default and will not be able to be disabled.


This issue could occur for Gallery Admins and all users.

  • If the issue is only for all the users or some particular users, then follow solution A
  • If the issue is occurring for all the admins/curators and users then follow solution B



Solution A 

  1. At least one admin/curator should log in successfully and access the admin page
  2. Under Admin page --> Click on Configuration
  3. Enable Users Can Register 


Solution B

Please submit a case with Alteryx support mentioning this article.

Additional Resources


This error can also be observed if there is any rules blocking the URL at WAF end. Need to check on Azure