User created date

[krakazyabra]

How to use GitHub

• Please use the 👍 reaction to show that you are interested into the same feature.
• Please don't comment if you have no relevant information to add. It's just extra noise for everyone subscribed to this issue.
• Subscribe to receive notifications on status change and new comments.

Is your feature request related to a problem? Please describe. Hi! It will be nice to see in occ user:info the date and time, when user was created. For now there is only last_seen value. But sometimes there is need to know also the creation date.

Describe the solution you'd like Add to occ user:info new key with creation date and time

Describe alternatives you've considered To have this information in interface in /settings/users

EDIT:

• [ ] #48649

[szaimen]

cc @nextcloud/server-triage is this feasible?

[ghost]

This issue has been automatically marked as stale because it has not had recent activity and seems to be missing some essential information. It will be closed if no further activity occurs. Thank you for your contributions.

[krakazyabra]

/reopen

[dabch]

Hi, I'm also needing this functionality in the API. If there is interest from the maintainers and I could get some guidance, I'd be willing to implement this myself. Shouldn't be too complicated, right? Thanks!

[szaimen]

If there is interest from the maintainers and I could get some guidance, I'd be willing to implement this myself. Shouldn't be too complicated, right?

Of course, please go ahead :)

[glanzel]

@dabch: did it work? that would be great.

[dabch]

I haven't been able to spend any time on this issue and probably won't in the future. Sorry!

[sorbaugh]

Some thoughts discussing with the Files team:

• we need to define it a bit better, since we can't always show the created-date for example if it is an LDAP user.
• In some cases we could show "first login", but would be misleading to show as "creation date"

cc @come-nc maybe you can provide more examples so we can refine the scope

cc @AndyScherzinger @marcoambrosini

[sorbaugh]

@krakazyabra @AndyScherzinger, since depending on the way users login, we might not have a "creation date" per se, what we propose to do:

Backend part

• Show First login date and show as "First Login" -> quite easy to do as logic can be reused from "Last Login"
• Also show "Creation date" but would be empty if not available -> We'll need to see which backends gives us the chance to fetch this info.
• Show it on the occ user:info as requested in the issue

Frontned

• [ ] Show "First Login" and "Creation Date" it on the account Management Table as new columns

[come-nc]

Ref for LDAP: https://datatracker.ietf.org/doc/html/rfc4512#section-3.4 (createTimestamp)

[marcoambrosini]

we can't always show the created-date for example if it is an LDAP user

Then would it make sense to just show first login for everyone instead of first created?

[pierreozoux]

Hi!

I'm following this issue in the context of developing a SCIM service provider as a Nextcloud application. (There is a link in the README to this issue :) )

SCIM, for those who don't know, is interesting in the context of using an SSO (SAML or OIdC), without ldap, to be able to sync user and group events (create, read, update, delete) from Id provider (SCIM client) (in our case keycloak), to a service provider (in our case Nc).

If you read the RFC page 17, it states that:

the attributes "id" and "meta" (and its associated sub-attributes) MUST be assigned values by the service provider.
...
meta.created:  The "DateTime" that the resource was added to the service provider.  This attribute MUST be a DateTime.

So in our case, we'd like to have the user creation date in Nextcloud registered in database somewhere. The Id provider creation date, is the responsibility of the Id provider.

Hope it helps to give context why and how this feature would be useful for us.

[come-nc]

@pierreozoux It’s unexpected to me that your application is not defining a user backend. If we add a user creation info, it will be managed by the user backend. The database backend will store it in database but other backends will fetch it elsewhere, or not provide it at all if it’s not known.

[sunetfreitag]

We would also like to see this feature due to a few advantages:

• With a createTimestamp you can distinguish between new users that never logged on and old users that never logged on
• A createTimestamp can be used to distinguish between recently created users that never logged on, and old users that never logged on
• A createTimestamp could be used to remind users to log on after a certain time, but also to deactivate an account if they did not log on after a defined amount of time (e.g., one or two weeks)

In addition, for security-critical Nextcloud instances, it might be required to add a second factor (NIS2?). Many created user accounts with no user logged on increase a potential attack where a rogue actor could hijack one of the newly created accounts and add their own MFA.