toro portlet install

[alex]

hi
I am in middle of trying install the toro portlets on to uportal 2.6.

in the install instructions , i am not sure how to configure Person
Attributes to use user.login.id . we are trying to get it to work in
2.6 ga. is that even the best version to use toro portlets?

thanks for the help

alex

[Andrew Wills]

Alex,

2.6.0 GA has 'user.login.id' configured by default, by way of an
example. Here's the line from personDirectory.xml:

<entry key="USER_NAME"><value>user.login.id</value></entry>

The trouble is -- this example only works for database-backed user
accounts (not LDAP, CAS, etc.) because the only type of authentication
that's enabled by default in any uPortal release is the database
variety. But database authentication is only a toy example; no one
uses it in real portal deployments.

When you configure uPortal to work with your LDAP and/or CAS, you will
need to adjust personDirectory.xml to make sure the 'user.login.id
attribute' gets populated for users from those systems.

Look at the example LDAP configuration which is commented out at the
bottom of the file.

Cheers,

drew wills

[Alex C]

Hi ,
i tried to set user.login.id in personDirectory.xml file . i am not
sure if i did this correct.
below is what i tried to do in the ldap section of the file.

<entry key="employeeNumber">
<set>
<value>employeeNumber</value>
<value>user.login.id</value>
</set>
</entry>

did i do this correctly?

Sincerely,
Alex

[Andrew Wills]

Alex,

It looks correct. The 'key' is the name of the attribute in LDAP. and
the <value>s are the name(s) you want that attribute to have in the
portal.

So the 'employeeNumber' attribute in LDAP will be mapped to the
'user.login.id' attribute in the portal.

cheers,

drew wills

[alex]

thanks for your help.

alex

On Oct 10, 11:02 am, "Andrew Wills" <wills.d...@gmail.com> wrote:
> Alex,
>
> It looks correct. The 'key' is the name of the attribute in LDAP. and
> the <value>s are the name(s) you want that attribute to have in the
> portal.
>
> So the 'employeeNumber' attribute in LDAP will be mapped to the
> 'user.login.id' attribute in the portal.
>
> cheers,
>
> drew wills
>

[alex]

Hi again,

We are in the middle of getting the gateway sso portlet working in
uportal 2.5.3 . in the portal , portlet is not working correctly.
the error we are getting is
Error:
This channel failed to render

which log files and where should we start looking at?

alex

[Andrew Wills]

On 10/12/07, alex <alexch...@gmail.com> wrote:
> which log files and where should we start looking at?

There is a 'portal.log' file which (by default) is written to the
directory from which you start tomcat (probably bin/).

Also, if you're viewing the channel as a member of the 'Portal
Administrators' group, or if for some other reason you have the
'VIEW.DETAILS' permission within the CError channel, you will see a
handy button within the channel area that you can view to display the
stack trace.

This stack trace is immensely useful if it is short; long ones seem
to get cut off before the most important info (the bottom 'Caused By:'
clause) is displayed.

Feel free to share what you learn.

drew wills

[alex]

I figured out what was causing the problem.. it seems user.login.id
for some reason isn't mapped to ldap attribute uid.
we set it in the following manner in the ldap section ...
<attribute><alias>user.login.id</alias> <name>uid</
name></attribute>

so i am not sure what is going on then..

Alex

On Oct 12, 12:08 pm, "Andrew Wills" <wills.d...@gmail.com> wrote: