Nope, the start page (http://partnerpage.google.com/example.com) is not XHTML enabled.
However if in your mobile browser you go to Gmail, Google Calendar, or Google Documents, i.e.: http://mail.google.com/a/example.com http://calendar.google.com/a/example.com http://docs.google.com/a/example.com You should automatically be forwarded to their XHTML versions (after signing in through SSO): http://mail.google.com/a/example.com/x/ http://calendar.google.com/a/example.com/m http://docs.google.com/a/example.com/m -alex On Nov 13, 7:14 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > Is personalized start page a XHTML-enabled application? This is the > page we are redirecting users too (we added an additional point in the > authentication chain). This was the page that initally prompted me to > add the test. > If it is a XHTML-enabled app, then the real source of my problem is > the use of js?? I have already done all of the other steps. The > mobile start page for my "standard gmail" account is really what got > be excited about this. > > Thanks again. > > On Nov 8, 5:22 am, "Alex (Google)" <[EMAIL PROTECTED]> wrote: > > > Hi, > > > Thanks for bringing this up. We're working on some docs describing > > how to make SSO work with mobile browsers, but here it is in a > > nutshell: > > > 1. base64-encode the SAMLResponse. Use a hidden input instead of an > > invisible textarea for the SAMLResponse and RelayState. > > > 2. Make sure your sign in form and the subsequent form which submits > > to the ACS URL both validate as XHTML (WAP isn't supported, but XHTML > > is). e.g. run it through: > > >http://validator.w3.org/ > > > 3. Don't rely on javascript. > > > 4. Er, the ACS URL currently uses javascript to redirect. But there > > is an internal flag to switch back to using HTTP 302 redirect > > (Internet Explorer complains about this). Submit a support request > > (instructions and PINs are in the control panel) if you would like to > > switch to HTTP redirect for your domain. > > > I believe the XHTML-enabled applications (Gmail, Google Calendar, > > Docs) can determine whether the XHTML version should be rendered, so > > you shouldn't need to manually specify the XHTML URL. > > > -alex > > > On Nov 7, 7:13 am, "[EMAIL PROTECTED]" <[EMAIL PROTECTED]> wrote: > > > > Reading through some of the older posts, I ran across a question about > > > SSO and mobile browsers. The post was "Login using SAML in a WAP > > > Browser". At that time, I understand that the SSO mechanism did not > > > support mobile browsers. Is this still the case? > > > > Before I cruised the message boards, added a sniffer to my login > > > application to test for mobile browsers and to change the relay state > > > to the mobile inbox. I am actually having success with authentication > > > from my blackberry 8800, however it is not a complete win. > > > > The browser stalls on the acs app, but if, when i reach this state, > > > ask for my mailbox (by entering the > > > urlhttps://mail.google.com/a/spartan.uncg.edu/x/) > > > it does show me my inbox. --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Google Apps APIs" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/google-apps-apis?hl=en -~----------~----~----~----~------~----~------~--~---
