Daniel McCallum schreef:
> Jon,
>
> Unless I'm very much mistaken, it shouldn't be necessary for a user to
> log in "before they can be added as a participant." So long as a
> user's EID can be resolved to a local or provided set of user
> attributes, the corresponding user _should_ be addable to any given
> worksite.
Your not mistaken, Jon. I'm developing a tool that creates user accounts
and adds them as participants to sites in a single step. Users can be
joined in sites before they've logged on.
Maarten
>
> Theoretically, it's valid for UIDs to equal EIDs, and I know some
> schools run just such a configuration. However, in general, EIDs are
> understood to be owned by an external system of record and as such are
> intended to be mutable, whereas UIDs are intended as opaque, immutable
> database keys. Thus, in an ideal world, EIDs are stored only once in
> the Sakai database, but UIDs can be stored repeatedly as
> pseudo-foreign keys. If it's actually true that your EIDs never ever
> change, then you could probably get away with generating
> SAKAI_USER_ID_MAP rows where USER_ID = EID, but without fully
> understanding the motivation for pre-populating those rows, I would
> generally advise against taking such risks (i.e., of scattering
> potentially mutable FKs around your database).
>
> FWIW, /portal/site/~[EID] urls will resolve the correct MyWorkspace
> sites, even if UIDs != EIDs. But I understand that GUID-based
> MyWorkspace site IDs can be annoying in other contexts. There is a
> patch out there (
http://bugs.sakaiproject.org/jira/browse/SAK-10299),
> though, that makes it easier for admins to find MyWorkspace sites by EID.
>
> Hope that helps.
>
> - Dan
>
> Jon Wheat wrote:
>> Jon's stupid question of the day ...
>>
>> Our faculty are having an issue with the 'they have to log in before
>> they
>> can be added as a participant' thing.
>>
>> So I manually added a test account to the SAKAI_USER_ID_MAP ( GEORGET )
>> this user is an LDAP user, not a local user and I made both the
>> USER_ID and
>> EID GEORGET
>> is that ok since most of the USER_IDs are a random hashish looking
>> thing?
>>
>> Seems better this way since I can add him as a participant and it
>> pulls his
>> name from LDAP etc.
>> Plus it creates a Site id of : ~georget
>>
>> Any warnings with me moving forward with this concept?
>>
>> - Jon
>>
>>
>>
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> ..:: I've learned that 'impossible' is a perception based on your
>> skills.
>> Jonathan Wheat / Developer
>> Luminis Developers Network
>> Messiah College, ITS
>> 717.766.2511 x3385
>> Personal Blog :
http://blogs.messiah.edu/wheat_world LDN - Luminis
>> Developer Network -
http://www.lumdev.net (
>>
http://www.lumdev.net/ )
>> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> [see attachment: "message0.html", size: 1617 bytes]
>>
>>
>> Attachments:
>>
>> message0.html
>>
https://collab.sakaiproject.org/access/content/attachment/a9153408-cb4f-49d0-007f-8a8c0373f86a/message0.html
>>
>>
>> ----------------------
>> This automatic notification message was sent by Sakai Collab
>> (
https://collab.sakaiproject.org/portal) from the DG: Development
>> (a.k.a. sakai-dev) site.
>> You can modify how you receive notifications at My Workspace >
>> Preferences.
>>
>
> ----------------------
> This automatic notification message was sent by Sakai Collab
> (
https://collab.sakaiproject.org/portal) from the DG: Development
> (a.k.a. sakai-dev) site.
> You can modify how you receive notifications at My Workspace >
> Preferences.
>
>
>
--
*Maarten van Hoof*
maarten.vanhoof@...
*Edia* - Educatie Technologie
Asterweg 19D12 | 1031 HL Amsterdam
*T* 020 716 36 12 | *F* 020 716 36 13 | *M* 06 245 392 15 | *www.edia.nl*
----------------------
This automatic notification message was sent by Sakai Collab (
https://collab.sakaiproject.org/portal) from the DG: Development (a.k.a. sakai-dev) site.
You can modify how you receive notifications at My Workspace > Preferences.