Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

[10:56:41 CDT(-0500)] <EricDalquist> so liferay doesn't return the username for getRemoteUser?
[11:01:53 CDT(-0500)] <athena> no, i believe it returns the internal ID
[11:02:31 CDT(-0500)] <athena> which is some long number
[11:02:40 CDT(-0500)] <EricDalquist> nice
[11:02:50 CDT(-0500)] <EricDalquist> yeah I don't think the spec is all that ambiguous there
[11:03:25 CDT(-0500)] <athena> yeah, i agree
[11:03:39 CDT(-0500)] <athena> i do think that there's potential ambiguity in what you actually want in some portlets
[11:03:49 CDT(-0500)] <EricDalquist> right
[11:03:56 CDT(-0500)] <EricDalquist> 286 helps a little there
[11:04:01 CDT(-0500)] <athena> like say for an email portlets, there's a good chance that you want the institutional string id, and a good chance that is what the user logged in using
[11:04:02 CDT(-0500)] <EricDalquist> by also giving you access to a "windowId"
[11:04:23 CDT(-0500)] <athena> but actually maybe your email system requires you to log in with your email address instead of your username
[11:04:30 CDT(-0500)] <EricDalquist> yup
[11:04:36 CDT(-0500)] <athena> most of our portlets get the username for cases like that, rather than actually determining the user
[11:05:00 CDT(-0500)] <EricDalquist> yeah those cases USER_INFO makes more sence
[11:05:10 CDT(-0500)] <EricDalquist> I'd still like to get the features we talked about in the long-dead 3.x code
[11:05:24 CDT(-0500)] <EricDalquist> of having the option to map data from the portlet.xml at publish time