[MGNLEE-117] Accesses not registered for ldap users Created: 18/Sep/08  Updated: 19/Mar/10  Resolved: 19/Mar/10

Status: Closed
Project: Magnolia DX Core
Component/s: None
Affects Version/s: 3.6.1
Fix Version/s: None

Type: New Feature Priority: Major
Reporter: Oscar Poves Hernanez Assignee: Magnolia International
Resolution: Obsolete Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified
Environment:

VMWare Infraestructure, asigned 2 CPU 3,0Ghz , 6GB of RAM, linux RHEL 5 X64, we have assigned to magnolia process 3,5GB , I'm using ldap connector but we implement an Custom LDAP Module but the problem also happens without using the module.


Issue Links:
Cloners
clones MGNLEE-95 Accesses not registered Closed
duplicate
duplicates MAGNOLIA-2166 Tools/accesses shows an empty list Closed
supersession
is superseded by MAGNOLIA-764 Add log/audit trail functionality Closed
Template:
Acceptance criteria:
Empty
Date of First Response:

 Description   

In the menu of magnolia called 'Tools', in his menu has another menu entry called Accesses. Here come the last of users access to server magnolia, in my case it appears nothing. For the repository users works but when we use the ldap connector does't work.



 Comments   
Comment by Magnolia International [ 26/Sep/08 ]

This is not a bug. As I said on MAGNOLIA-2166, this has never and will never work (until we implement it differently, that is) work external users.

Are your users replicated in Magnolia ?

Comment by Oscar Poves Hernanez [ 29/Sep/08 ]

The users are only in LDAP.

Comment by Philipp Bracher [ 30/Sep/08 ]

We will use a log file to log the logins/logouts. This has the following benefits:

  • independent of the implementation (no user node needed)
  • complete history (not only the last access of a user)
  • rather trivial to implement (log statements in the login mechanism)
Comment by Magnolia International [ 19/Mar/10 ]

Fixed long ago with MAGNOLIA-764

Generated at Mon Feb 12 05:26:52 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.