[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-12 Thread Roel de Brouwer (werk)
Is it "Compute" --> "App Engine" --> "Instances" --> "Shutdown" and "Compute" --> "App Engine" --> "Memcache" --> "Flush cache" Op vrijdag 12 juni 2015 09:29:50 UTC+2 schreef Roel de Brouwer (werk): > > Can you tell me where I can do that in the Console? The person that build > the backend of o

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-12 Thread Roel de Brouwer (werk)
Can you tell me where I can do that in the Console? The person that build the backend of our app is not in the house today. Op donderdag 11 juni 2015 23:55:12 UTC+2 schreef Arun Nedun: > > Right. Shutdown instance and clear cache. > > On Thursday, June 11, 2015 at 4:26:51 PM UTC-4, Douglas Meredi

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Arun Nedun
Right. Shutdown instance and clear cache. On Thursday, June 11, 2015 at 4:26:51 PM UTC-4, Douglas Meredith wrote: > > I'm still seeing the problem. Did you guys have to bounce your instances > or something to get things back on track? > > > > On Thursday, June 11, 2015 at 1:19:11 PM UTC-7, Nhat

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Douglas Meredith
I'm still seeing the problem. Did you guys have to bounce your instances or something to get things back on track? On Thursday, June 11, 2015 at 1:19:11 PM UTC-7, Nhat Nguyen wrote: > > Confirmed, everything seems to be back to normal. > > четвъртък, 11 юни 2015 г., 22:31:01 UTC+3, Arun Nedun

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Nhat Nguyen
Confirmed, everything seems to be back to normal. четвъртък, 11 юни 2015 г., 22:31:01 UTC+3, Arun Nedun написа: > > The issue now appears to be fixed for me..! Can someone else confirm this > as well? Will do more checking now... > > On Thursday, June 11, 2015 at 8:34:30 AM UTC-4, Erik Zivkovic w

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread ivbar bar
Yes, it's working now. Ahh... -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To post to this group, send em

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Arun Nedun
The issue now appears to be fixed for me..! Can someone else confirm this as well? Will do more checking now... On Thursday, June 11, 2015 at 8:34:30 AM UTC-4, Erik Zivkovic wrote: > > I am using code from > http://android-developers.blogspot.se/2013/01/verifying-back-end-calls-from-android.html

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Nathan Green
Anyone have any updates on this? It has been down all day On Thursday, June 11, 2015 at 8:34:30 AM UTC-4, Erik Zivkovic wrote: > > I am using code from > http://android-developers.blogspot.se/2013/01/verifying-back-end-calls-from-android.html > > and have been using it for a long time to authen

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Tom Edge
Does this work when using the cloud endpoints @Api annotations to declare endpoint api methods? I can't work out how to implement your workaround On Thursday, June 11, 2015 at 4:29:28 PM UTC+1, Erik Zivkovic wrote: > > You can subclass GoogleIdTokenVerifier for now > > package com.my.project.pack

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread ivbar bar
Looks like it will not work with app engine + cloud endpoints. Do you have solution for it? Thanks -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Erik Zivkovic
You can subclass GoogleIdTokenVerifier for now package com.my.project.package; import java.io.IOException; import java.security.GeneralSecurityException; import java.security.PublicKey; import com.google.api.client.auth.openidconnect.IdTokenVerifier; import com.google.api.client.googleapis.aut

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Roel de Brouwer (werk)
What the actual heck? But why are so few people that suffer from this? I can only found two results about this topic. Since this day the Android app can't connect anymore with the backend. -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. T

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Nhat Nguyen
I am experiencing the same issue now. I have to temporary disable authentication. четвъртък, 11 юни 2015 г., 15:34:30 UTC+3, Erik Zivkovic написа: > > I am using code from > http://android-developers.blogspot.se/2013/01/verifying-back-end-calls-from-android.html > > and have been using it for

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Tom Edge
Yes, I've got the same problem. I've asked a question on Stack Overflow here https://stackoverflow.com/questions/30781799/google-cloud-endpoints-verifytoken-signature-length-not-correct Have you found any kind of workaround yet? Tom On Thursday, June 11, 2015 at 1:34:30 PM UTC+1, Erik Zivkovic

[google-appengine] Re: Getting "Security issue: Signature length not correct: got 256 but was expecting 128" since about one hour ago.

2015-06-11 Thread Tom Edge
Yes, I've got the same problem. I've asked a question on Stack Overflow here https://stackoverflow.com/questions/30781799/google-cloud-endpoints-verifytoken-signature-length-not-correct Have you found any kind of workaround yet? Tom On Thursday, June 11, 2015 at 1:34:30 PM UTC+1, Erik Zivkovic