OBEROn - Bug Trace - Oberon Platform
Viewing Issue Advanced Details
ID: Category: Severity: Reproducibility: Date Submitted: Last Update:
109 Platform functionalities feature have not tried 2014-07-16 09:52 2014-08-03 10:38
Reporter: g_prajeesh Platform:  
Assigned To: administrator OS:  
Priority: normal OS Version:  
Status: feedback Product Version: 4.1 - DB build 0071  
Product Build: Resolution: open  
Projection: none      
ETA: none Fixed in Version:  
Summary: 0000109: Need to link Oberon Users with Enterprise AD Servers and Sync
Description: Most of the organization manages their User/ Group information in AD Server. Is it possible to have a seamless integration with LDAPServer so that it can be integrated with Oberon. It should be possible to differentiate Oberon user from other users in the AD System.

Basically, In Oberon we will have basic userId, email, Full Name details and can have optional link to AD Server so that any additional read only information configuration can be fetched from AD. This will pave the way for Single sign on, enable / disable user if he leaves the company etc..
Steps To Reproduce:
Additional Information:
Relationships
Attached Files:
Issue History
Date Modified Username Field Change
2014-07-16 09:52 g_prajeesh New Issue
2014-07-16 16:33 administrator Status new => assigned
2014-07-16 16:33 administrator Assigned To => administrator
2014-08-03 10:38 administrator Note Added: 0000181
2014-08-03 10:38 administrator Status assigned => feedback
2014-08-03 10:39 administrator Note Edited: 0000181

Notes
(0000181)
administrator   
2014-08-03 10:38   
(edited on: 2014-08-03 10:39)
The OBEROn users have the following attributes:

name (the userID)
password
description (the Full Name)
application
hidden (the hidden flag)
origdate (creation date)
moddate (modification date)
moduser (modification user)
svnrev (synchronization counter for SVN repository)
image (true = has icon ; false = no icon)
imagedata (binary data: icon bitmap)
lastaccess (last access date / time)
address
telephone
fax
superuser (the super user flag)
language (the default language)
mail (email address)
mail type (email type: internal / external / both )
password active
password enabled
localarea (default localarea)
objectspace (default objectspace)
metricsystem (assigned metric system)
ownassignment (list of assignments)
ownteam (list of teams)
systemaccess (list of system access privileges)
adminaccess (list of admin access privileges)
basicaccess (list of basic access privileges)

- which of them should be retrieved from the LDAP server when the user perform the login to the system?
- who will update these information on the LDAP server? By which tool?
- the user information will be read only when the user accesses to the system and discarded when he logs out? [ in this case, the user needs to logout to get the new values ]