SAML configure about reportportal

[MaryiaRymarchyk]

@srikar6118686 could you provide more details please. What version of RP do you use? What error do you see?
You mentioned that one team has successfully configured SAML, was this done for the same RP instance as you ?

[srikar6118686]

@MaryiaRymarchyk Currently we are using the 5.7.4 version. After authenticating it is not redirecting to my URL it is going to another team's URL. It is a different RP instance.

[raikbitters]

Hello @srikar6118686.

I'm sorry, but I am unsure about what it is that you are trying to configure.

Usually, in IdP, one SSO Application matches with one ReportPortal instance. If you get redirection to another RP instance, you must create a separate Application for your instance in your SSO provider.

[srikar6118686]

@MaryiaRymarchyk @raikbitters Can we have a call to discuss in detail?

[MaryiaRymarchyk]

@srikar6118686 sorry, but we do not provide on-call support, and all our team are busy with production tasks. In addition we assume that your issue is not related to RP. However if you provide more detailed info we'll try to help you.
Could you please provide screenshots of 1) SAML configuration from Report portal integration and 2)configuration of Identity provider.
Please describe the steps what are you doing, What you expect and what is the actual result (with screens if it is possible).

[srikar6118686]

@MaryiaRymarchyk,

1.Configuration
Identity provider name ID:
urn:oasis:names:tc:SAML:1.1:nameid-format:unspecified
Provider name:
TRSSO
Metadata URL:
https://sso.thomsonreuters.com/pf/federation_metadata.ping?PartnerSpId=cr.report.portal.sp.id
Email:
user.email
RP callback URL:
https://cr-reportportal.1129.aws-int.thomsonreuters.com/uat
Name attributes mode:
First & last name
First name:
user.firstName
Last name:
user.lastName

2. this is my URL https://cr-reportportal.1129.aws-int.thomsonreuters.com/ui/ and when I try to log in to https://cr-reportportal.1129.aws-int.thomsonreuters.com/ui/ URL with the help of sign-in with SAML then it throws This site can’t be reachedreportportal-stable.1624.aws-int.thomsonreuters.com unexpectedly closed the connection.
   Try:

Checking the connection
Checking the proxy and the firewall
ERR_CONNECTION_CLOSED

[MaryiaRymarchyk]

@srikar6118686 thank you for provided details.
We assume that issue may be in callback URL.
Could you please share the screenshots of 1) SAML configuration from Report portal integration and 2)configuration of Identity provider.

[srikar6118686]

@MaryiaRymarchyk ,PFA

[raikbitters]

Hello @srikar6118686. There are two different urls:
https://cr-reportportal.1129.aws-int.thomsonreuters.com/ui/
reportportal-stable.1624.aws-int.thomsonreuters.com

I guess you have a configuration on your identity provider side that makes a callback to report portal-stable.1624.aws-int.thomsonreuters.com. You need to change this configuration and specify the expected URL https://cr-reportportal.1129.aws-int.thomsonreuters.com/ui/. It doesn't appear to be an issue with ReportPortal.

[srikar6118686]

@MaryiaRymarchyk Sure, I'll check with my SSO enablement team and keep you posted.

[srikar6118686]

@raikbitters, I made changes as per your suggestion but still we are having an issue.

[srikar6118686]

@MaryiaRymarchyk / @raikbitters / @tsteenbe / @lexecon the SSO team provided the IDP URL even after it threw 405 error( 405 Not Allowed nginx)

PFA, and help me out.

[srikar6118686]

@DzmitryHumianiuk Could you please assign any person to resolve this issue?

[DzmitryHumianiuk]

@srikar6118686 For expedited support, we offer paid services. Please check here for more details:
https://reportportal.io/pricing/on-premises

[srikar6118686]

@DzmitryHumianiuk Sure, I'll discuss it with my management and get back to you. Meanwhile, try to help us.

[raikbitters]

@MaryiaRymarchyk / @raikbitters / @tsteenbe / @lexecon the SSO team provided the IDP URL even after it threw 405 error( 405 Not Allowed nginx)

PFA, and help me out.

Hello @srikar6118686. I see you have a correct redirect right now. However, It looks like you have some restrictions on your Load balancer/Edge server (Nginx).

[srikar6118686]

@raikbitters, Is Report Portal not being served using Nginx, or is Nginx not installed on your server?
I tried to edit load balancer rules but as per Cloudwatch, it is trying to reach the URL. We tried to edit the nginx service but I couldn't find any where.

[raikbitters]

@srikar6118686 we use Nginx ingress-controller by default. However I don't have any Ideas about your infrastructure and how you config it. You can have additional Nginx instance as a Single entry point or you can change our ingress-config. Out of the box it works fine 🙂 I'm not sure that we can solve your problem without looking into your infrastructure config.