Hi,
As per the discussion in [1], this issue can arise due to a certificate
mismatch of portal and your IdP.
Can you please check whether you can follow suggested solutions?
[1] http://mail.wso2.org/mailarchive/dev/2015-January/042262.html
Thanks.
On Wed, Jun 1, 2016 at 2:08 PM, Megala Uthayaku
Hi Farasath,
I have used only response signing on. But still I have the same issue.
Thanks.
On Wed, Jun 1, 2016 at 12:46 PM, Farasath Ahamed wrote:
> Hi Megala,
>
> Have you enabled Signature validation for Authentication requests? If so
> can you try the scenario with only Response signing o
Hi Megala,
Have you enabled Signature validation for Authentication requests? If so
can you try the scenario with only Response signing on and see if it works
for tenants as well.
Thanks,
Farasath Ahamed
Software Engineer,
WSO2 Inc.; http://wso2.com
lean.enterprise.middleware
Email: farasa..
Hi All,
We embedded the dashboard not using SSO, but with custom Jaggery page
inside "admin-dashboard" app. So the authentication session with
"admin-dashboard" is sufficient for all auth/authz purpose. Hence the above
problem does not arise.
Therefore that work is not technically related to this
ok. I will check with him. Thanks
On Wed, Jun 1, 2016 at 11:46 AM, Nuwan Dias wrote:
> Ruwan worked on embedding the portal within the admin-dashboard. Can you
> please talk to him and see what this means in that context?
>
> On Wed, Jun 1, 2016 at 11:43 AM, Megala Uthayakumar
> wrote:
>
>> No.
Ruwan worked on embedding the portal within the admin-dashboard. Can you
please talk to him and see what this means in that context?
On Wed, Jun 1, 2016 at 11:43 AM, Megala Uthayakumar wrote:
> No. This is the portal coming from carbon-dashboard feature. It is
> different from admin-dashboard. P
Portal in the sense admin-dashboard right?
On Wed, Jun 1, 2016 at 11:33 AM, Megala Uthayakumar wrote:
> I have already mounted the registry and publisher app is working fine in
> tenant mode as well. This issue only exists in the portal app.
>
> Thanks.
>
> Regards,
> Megala
>
> On Wed, Jun 1, 2
I have already mounted the registry and publisher app is working fine in
tenant mode as well. This issue only exists in the portal app.
Thanks.
Regards,
Megala
On Wed, Jun 1, 2016 at 11:26 AM, Nuwan Dias wrote:
> You need to share the same registry (mount registries) between IS and APIM
> to m
You need to share the same registry (mount registries) between IS and APIM
to make this work for tenants.
Its because tenants have their key stores in the registry and the SAML
response is signed using the key in this key store. If they don't share the
registry signing will be done by one key and
It is working when I remove that signature validation part from acs.jag
On Wed, Jun 1, 2016 at 9:35 AM, Udara Rathnayake wrote:
>
>
> On Wed, Jun 1, 2016 at 8:53 AM, Megala Uthayakumar
> wrote:
>
>> Hi All,
>>
>> I am trying to configure SSO in APIM 2.0.x by following [1]. Publisher
>> and Stor
Hi Megala,
Enabling debug for oauth2 and sso on the server where your IDP is located
you can get something what is happening when they try to log in.
log4j.logger.org.wso2.carbon.identity.oauth2=DEBUG
log4j.logger.org.wso2.carbon.identity.sso.saml=DEBUG
maybe you are just not validating with the
On Wed, Jun 1, 2016 at 8:53 AM, Megala Uthayakumar wrote:
> Hi All,
>
> I am trying to configure SSO in APIM 2.0.x by following [1]. Publisher and
> Store jaggery apps work as expected but when I try to login to portal
> app(Portal of Dashboard Server) using SSO, it works fine when I am logging
>
Hi All,
I am trying to configure SSO in APIM 2.0.x by following [1]. Publisher and
Store jaggery apps work as expected but when I try to login to portal
app(Portal of Dashboard Server) using SSO, it works fine when I am logging
in as super-tenant user but whenever I try to login in as a user from
13 matches
Mail list logo