Migrating Web Reports from Root to stand-alone, having SAML issues. Help?

Usage and Config Platform
1

Installed Web Reports on a new server using the Server installer. Backed up database from old Root instance, restored to new server. Now I can’t log in. :joy:

The New server is reporting itself to our SAML authentication as the Root server:

The entityID in the request was '<root server name>'.
The assertion consumer service URL in the request was '<new server name>/saml'.

Am I going about this the wrong way? Is there something else I need to update/edit?

I mean, I didn't expect it to work right off the bat, but the only thing I brought over was the database and the masthead. Looking through the database, I can't find a table that appears to hold the original server name.

It appears from the log file that scheduled activities are firing off from the new server, so I guess that's a good sign? I just can't log in to it... :confused:

/cc @JasonWalker (since I know he’s done something similar before…)

2

You need to define the hostname of the new Web Reports server as entry point in the SAML configuration of the platform you are using for authentication (ADFS/Okta/Entra/etc). For what it is worth, we have 3 web reports servers within our environment and as long as all are defined as entry points,it should work with a single SAML configuration. Here is the documentation: How to configure BigFix to integrate with SAML 2.0

1 Like
3

Pretty sure I did that, but I’ll have to check again…

4

Oy…. I knew as soon as I asked, it’d be something easy. I’d forgotten about the port number (either adding it to the entry point or changing it to 443). Working great now. Thanks!

3 Likes