#3860 Refactor session recording to only use cache_req
Closed: cloned-to-github 2 years ago by pbrezina. Opened 3 years ago by sbose.

The main task for SSSD related to session recording is to find out based on the configuration options if a user should be recorded or not. As a result the 'sessionRecording' attribute is added to the cached user object with the values 'true' or 'false'.

Currently the code doing this is spread between the cache_req code (cache_req_sr_overlay_match_users() and cache_req_sr_overlay_match_all_step_done()), the common responder code (dp_req_initgr_pp_sr_overlay()) and since recently in the files provider (sf_enum_files() calling dp_add_sr_attribute()).

Although iirc it was me who originally asked to have as much code as possible for this in the backend I think nowadays it would make maintenance of the code easier if everything would be handled in the cache_req overlay code.


Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.1

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.2 (was: SSSD 2.1)

3 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 2.3 (was: SSSD 2.2)

2 years ago

Metadata Update from @thalman:
- Issue tagged with: Future milestone

2 years ago

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/4850

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @pbrezina:
- Issue close_status updated to: cloned-to-github
- Issue status updated to: Closed (was: Open)

2 years ago

Login to comment on this ticket.

Metadata