Originally created by @skycorrigan on GitHub (May 14, 2025).
Hello again. After submitting the access log suggestion, I started thinking about some other additions for Pangolin.
Here's a few:
Authorization time limit: Have a setting where users must re-auth after a certain number of hours/days/months or never at all. This would be great for security in the event a user's credentials and/or session were stolen or hijacked. With that, an option to bump sessions would be great for admins if we noticed malicious behavior (this would go in-hand with my suggestion of an access log).
Account disable/re-enable/ban: Another security addition and would go in hand with suggestion #1.
That's all for now. Thank you again.
Originally created by @skycorrigan on GitHub (May 14, 2025).
Hello again. After submitting the access log suggestion, I started thinking about some other additions for Pangolin.
Here's a few:
1) Authorization time limit: Have a setting where users must re-auth after a certain number of hours/days/months or never at all. This would be great for security in the event a user's credentials and/or session were stolen or hijacked. With that, an option to bump sessions would be great for admins if we noticed malicious behavior (this would go in-hand with my suggestion of an access log).
2) Account disable/re-enable/ban: Another security addition and would go in hand with suggestion #1.
That's all for now. Thank you again.
Number 2 for enabling and disabling users is a good idea so you dont have to delete their whole account! Just to keep things clean would you mind closing this pull request and opening a discussion feature request for that feature?
@oschwartz10612 commented on GitHub (May 14, 2025):
Hi! Thanks for the suggestions again!
I think number one might have already been suggested in https://github.com/orgs/fosrl/discussions/480 and https://github.com/orgs/fosrl/discussions/365.
Number 2 for enabling and disabling users is a good idea so you dont have to delete their whole account! Just to keep things clean would you mind closing this pull request and opening a discussion feature request for that feature?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @skycorrigan on GitHub (May 14, 2025).
Hello again. After submitting the access log suggestion, I started thinking about some other additions for Pangolin.
Here's a few:
Authorization time limit: Have a setting where users must re-auth after a certain number of hours/days/months or never at all. This would be great for security in the event a user's credentials and/or session were stolen or hijacked. With that, an option to bump sessions would be great for admins if we noticed malicious behavior (this would go in-hand with my suggestion of an access log).
Account disable/re-enable/ban: Another security addition and would go in hand with suggestion #1.
That's all for now. Thank you again.
@oschwartz10612 commented on GitHub (May 14, 2025):
Hi! Thanks for the suggestions again!
I think number one might have already been suggested in https://github.com/orgs/fosrl/discussions/480 and https://github.com/orgs/fosrl/discussions/365.
Number 2 for enabling and disabling users is a good idea so you dont have to delete their whole account! Just to keep things clean would you mind closing this pull request and opening a discussion feature request for that feature?
@skycorrigan commented on GitHub (May 14, 2025):
My fault. I overlooked the discussion tab. Will close this out now.