[ 
https://wso2.org/jira/browse/MASHUP-874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Yumani Ranaweera closed MASHUP-874.
-----------------------------------


Not a bug. Closing the JIRA.

> Error when signing-in with Open ID 
> -----------------------------------
>
>                 Key: MASHUP-874
>                 URL: https://wso2.org/jira/browse/MASHUP-874
>             Project: WSO2 Mashup Server
>          Issue Type: Bug
>          Components: Admin UI
>    Affects Versions: Nightly
>         Environment: WinXP, JDK1.5, IE7
>            Reporter: Yumani Ranaweera
>            Assignee: Channa Gunawardena
>             Fix For: 1.1
>
>         Attachments: OpenID.JPG
>
>
> My open ID login which I've been using was rejected after a while. I tried 
> restarting the server, deleting the cookies, restarting the machine, but the 
> server is not accepting my Open ID. Its prompting me to re-register instead 
> (see attached image).
> Steps:
> -------
> 1. Login to MS using a valid open ID
> 2. perform some tasks
> 3. Sign-out (or let a timeout happen)
> 4. Try signing-in using the same open ID again
> Issue:
> -------
> The error shown below appeared after the above step 4. 
> INFO [2008-07-02 10:59:56,562]  Starting discovery on URL identifier: 
> http://yumani.myopenid.com/
> INFO [2008-07-02 10:59:58,328]  Yadis discovery succeeded on 
> http://yumani.myopenid.com/
> INFO [2008-07-02 10:59:58,328]  Using Yadis normalized URL as claimedID: 
> http://yumani.myopenid.com/
> INFO [2008-07-02 10:59:58,328]  Discovered 3 OpenID endpoints.
> INFO [2008-07-02 10:59:58,328]  Trying to associate with 
> http://www.myopenid.com/server attempts left: 4
> WARN [2008-07-02 10:59:58,328]  Could not create association of type: 
> no-encryption:HMAC-SHA1:OpenID2
> WARN [2008-07-02 10:59:58,328]  Could not create association of type: 
> no-encryption:HMAC-SHA256:OpenID2
> INFO [2008-07-02 11:00:00,296]  Associated with 
> http://www.myopenid.com/server handle: {HMAC-SHA256}{4861d0d0}{ML3s7g==}
> INFO [2008-07-02 11:00:00,296]  Trying to associate with 
> http://www.myopenid.com/server attempts left: 4
> INFO [2008-07-02 11:00:00,296]  Found an existing association.
> INFO [2008-07-02 11:00:00,312]  Creating authentication request for 
> OP-endpoint: http://www.myopenid.com/server claimedID: 
> http://yumani.myopenid.com
>  OP-specific ID: http://yumani.myopenid.com/
> INFO [2008-07-02 11:00:00,312]  Return URL: 
> https://localhost:7443/identityaccept.jsp?calledfrom=signin&AuthenticationMethod=openid&FromIdentityProvi
> er=true matches realm: 
> https://localhost:7443/identityaccept.jsp?calledfrom=signin&AuthenticationMethod=openid&FromIdentityProvider=true
> WARN [2008-07-02 11:00:00,328]  RP discovery / realm validation disabled; 
> this option SHOULD be enabled for OPs
> INFO [2008-07-02 11:00:00,328]  Return URL: 
> https://localhost:7443/identityaccept.jsp?calledfrom=signin&AuthenticationMethod=openid&FromIdentityProvi
> er=true matches realm: 
> https://localhost:7443/identityaccept.jsp?calledfrom=signin&AuthenticationMethod=openid&FromIdentityProvider=true
> WARN [2008-07-02 11:00:00,328]  RP discovery / realm validation disabled; 
> this option SHOULD be enabled for OPs
> INFO [2008-07-02 11:00:05,109]  Verifying authentication response...
> INFO [2008-07-02 11:00:05,125]  Received positive auth response.
> WARN [2008-07-02 11:00:05,125]  Nonce is too old: 2008-06-25T05:00:05ZAy3DpB
> RROR [2008-07-02 11:00:05,125]  Nonce verification failed.
> RROR [2008-07-02 11:00:05,125]  Error in token verification
> rg.wso2.solutions.identity.relyingparty.RelyingPartyException: OpenID 
> verification failed
>        at 
> org.wso2.solutions.identity.relyingparty.openid.OpenIDConsumer.verifyOpenID(OpenIDConsumer.java:203)
>        at 
> org.wso2.solutions.identity.relyingparty.openid.OpenIDConsumer.setSessionAttributes(OpenIDConsumer.java:130)
>        at 
> org.wso2.solutions.identity.relyingparty.servletfilter.RelyingPartyFilter.doFilter(RelyingPartyFilter.java:61)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>        at 
> org.wso2.mashup.transport.ServiceUIFilter.doFilter(ServiceUIFilter.java:207)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>        at 
> org.wso2.adminui.AdminUIServletFilter.doFilter(AdminUIServletFilter.java:135)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:215)
>        at 
> org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188)
>        at 
> org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:210)
>        at 
> org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:174)
>        at 
> org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127)
>        at 
> org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117)
>        at 
> org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108)
>        at 
> org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:151)
>        at 
> org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:870)
>        at 
> org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665)
>        at 
> org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528)
>        at 
> org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81)
>        at 
> org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:685)
>        at java.lang.Thread.run(Thread.java:595)
> RROR [2008-07-02 11:00:05,343]  Identity based login failed. Reason:
> Steps

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://wso2.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

_______________________________________________
Mashup-dev mailing list
[email protected]
http://wso2.org/cgi-bin/mailman/listinfo/mashup-dev

Reply via email to