Gigya

Avatar

Avatar
Level 1
scottl-axis
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile

Avatar
Level 1
scottl-axis
Level 1

Likes

0 likes

Total Posts

2 posts

Correct reply

0 solutions
View profile
scottl-axis
Level 1

01-12-2017

In attempting to connect to an existing Gigya instance as an identity provider. I've followed the documentation on both the Adobe side and Gigya side but when I attempt to open the login view, the in-app browser closes before resolving the page and errors out.

I've narrowed this down to an issue with the Service provider ID but I can't find any information on what this ID should be. In all the example set ups I've found it's listed as https://es.publish.adobe.com/saml2

Is this correct? And if so, does anyone have experience with Gigya integrations?

Thanks

-Scott

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Level 1
gigya_customer_
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile

Avatar
Level 1
gigya_customer_
Level 1

Likes

0 likes

Total Posts

1 post

Correct reply

0 solutions
View profile
gigya_customer_
Level 1

04-12-2017

Hi Scott

It may also be worth opening a support case with the Gigya Tech Support team who may be able to assist here.

A case can be opened via the Gigya Admin Console/Support Portal using the customers credentials. They can set you up if required.

Regards

Jason Hodgkinson

Director, Support Engineering

Gigya EMEA

Avatar

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,409 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile

Avatar
Validate 25
Level 10
smacdonald2008
Level 10

Likes

1,409 likes

Total Posts

12,671 posts

Correct reply

2,278 solutions
Top badges earned
Validate 25
Validate 10
Validate 1
Give back 900
Give back 600
View profile
smacdonald2008
Level 10

02-12-2017

If you do not hear any information from the community on this use case - please contact support.