I'm adding Mathuriga and Nadeeshani to this thread as similar issue is
reported in the non-federated flow as well.
On Mon, Apr 16, 2018 at 3:13 PM Omindu Rathnaweera wrote:
> On Mon, Apr 16, 2018 at 5:45 AM, Darshana Gunawardana
> wrote:
>
>> AFAIR, this seems to be an issue with handling
On Mon, Apr 16, 2018 at 5:45 AM, Darshana Gunawardana
wrote:
> AFAIR, this seems to be an issue with handling email type usernames
> without enabling email usernames..
>
> Anyhow we have discussed to fix this from the sso consent implementation..
> @Omindu: Do we have any git
On Mon, Apr 16, 2018 at 9:15 AM, Darshana Gunawardana
wrote:
> AFAIR, this seems to be an issue with handling email type usernames
> without enabling email usernames..
>
Thanks Darshana for the input. It looks like that. I will configure some
other attribute (other than email)
AFAIR, this seems to be an issue with handling email type usernames without
enabling email usernames..
Anyhow we have discussed to fix this from the sso consent implementation..
@Omindu: Do we have any git issue related to this?
Thanks,
On Mon, Apr 16, 2018 at 9:01 AM, gayan gunawardana
Hi Tharindu,
On Mon, Apr 16, 2018 at 8:39 AM, Tharindu Edirisinghe
wrote:
> Hi Gayan,
>
> It seems the error is coming form the consent management feature. If you
> don't require this feature, you can simply turn it off from the following
> property in identity.xml file.
>
>
Hi Gayan,
It seems the error is coming form the consent management feature. If you
don't require this feature, you can simply turn it off from the following
property in identity.xml file.
*false*
Alternatively you can turn off the following listener from identity.xml
Hi All,
I have configured travelocity.com sample application as SAML inbound and
Facebook as federated authenticator for IS-5.5.0. After adding Facebook
credentials, got below UI.
​After enabling debug logs found below exception. Is there any further
configuration I have to do to get it work ?