Home » forums » Luminis Platform / System

uPortal Error on login from Android phone

Submitted by ahoward on Thu, 2010-07-22 13:30

If I try to log into our portal from a phone running Android 2.1 or 2.2, I get an error:

uPortal Error
Sorry, but uPortal encountered an error that is preventing it from rendering. The error must be corrected by system administrators. Try again later

Being the portal administrator, I've tried contacting myself to correct it, but I'm stumped. A friend with version 1.6 of Android on his phone has no problem. I've tried switching the user agent, tried from a real phone and from the Android SDK's emulator, but no dice.

Sungard Support was kind enough to open a defect 1-COTA77 for me, but let me know not to expect much because it's not a supported browser.

Anyone have any ideas about what's causing the problem and what to do to fix it?

‹ Segmentation Fault - core dumped during III -> 4 migration (import) iPerson & JSP for Luminis IV ›

Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

android login

Submitted by Jason on Tue, 2010-07-27 15:51.

I have an HTC incredible, running 2.1, and it logs into our portal without error.

However, one of my colleagues had a nexus one, and it did not work. We never did figure out why. Try a different browser, like Opera Mini or Dolphin perhaps? Both are available in the android market.

Same issue with android

Submitted by mcshell on Tue, 2010-07-27 17:12.

We are also having the same issue but with certain versions of android and not being able to log into the portal system. I have a motorola droid on 2.1, I am unable to access but my coworker has a sprint htc hero on android 1.6 that has no issue. We have also had a few students and staff complain about the same issue. Our resolution has been for users to use opera that can be downloaded from the market.

Thanks,
Mike

uPortal pages don't work, but admin pages do on android

Submitted by ahoward on Wed, 2010-07-28 11:13.

Even though it shows the uPortal error, Luminis apparently finishes the login process, at least enough so that once you get the error, you can paste in the URL for the System Administration Center (the Admin button) into the Android browser and work with those pages.

Opera Mini seems to mostly work for me, though letting Opera's servers be a man-in-the-middle for the secure connections isn't exactly ideal.

more info

Submitted by drlarsen on Thu, 2011-01-06 22:23.

We've also received complaints from students about this error. I tested it on a Galaxy S 2.1 and was able to reproduce.

I realized additional error details are available in the HTML source of the error message. It's commented out, so it doesn't render on the page, but you can view it on your Android by putting the following in the address bar:

javascript:alert(document.documentElement.innerHTML);

And the hidden error message:

System does not allow for unauthenticated non-guest users.
[specific data: ]
org.jasig.portal.security.PortalSecurityException: System does not allow for unauthenticated non-guest users.
at org.jasig.portal.UserInstanceManager.getUserInstance(UserInstanceManager.java:86)
at org.jasig.portal.PortalSessionManager.doGet(PortalSessionManager.java:283)

cookies

Submitted by rbalara on Fri, 2011-01-07 14:32.

We run into this as well. I think it has something to do with how cookies are handled during the handoff from the SSL login to the non-SSL login success page. If the cookie gets dropped by a browser at this page, it is seen as an unathenticated user trying to use an existing session. You can reproduce this in Firefox via an add-on called Tamper Data and modifying the headers on this step to remove the cookie. Unfortunately, there's no easy solution that I'm aware of.

missing JSESSIONID cookie

Submitted by drlarsen on Fri, 2011-01-07 18:58.

It looks like there's a problem right from the start with the JSESSIONID cookie not being stored. Searching around online it appears this is a bug with the default Android browser. The only solution people have found is to go cookieless, but I don't think that will work here.

Google Issue

Submitted by jmpimpo on Fri, 2011-01-14 11:52.

In researching this issue for my college, I stumbled across Issue 7978 in the Android Open Source Issue board that has to do with the authentication cookie drop. Here's the link to the issue if you would like to comment on it or follow it to bring Google's attention to the problem as one that needs solving: http://code.google.com/p/android/issues/detail?id=7978. If we can bring enough attention to it, maybe in the next Android update, the issue will be solved.

I'm doing Parallel

Submitted by scarpozzi on Sun, 2011-03-06 10:55.

I'm doing Parallel Deployment.... I've had no problem with my android phone working until late last week. I'm not sure if it's keeping an old cookie for the wrong server or what. At least it's obvious others are dealing with it as well. Knowing they registered a defect for it allows me to give our support teams the answer that it's not supported and may or may not work.

Syndicate content