Opened 3 years ago
Closed 3 years ago
#2542 closed task (fixed)
Revise the way SSH keys are stored in LDAP
| Reported by: | strk | Owned by: | |
|---|---|---|---|
| Priority: | normal | Milestone: | Sysadmin Contract 2020-II |
| Component: | SysAdmin | Keywords: | LDAP |
| Cc: | robe |
Description
We are probably doing it wrong by allowing multiple keys in a single attribute. See https://github.com/go-gitea/gitea/issues/13984#issuecomment-744494376
Ticket #2116 was about adding the LDAP attribute
Change History (3)
comment:1 by , 3 years ago
comment:2 by , 3 years ago
We're definitely doing this wrong: https://github.com/go-gitea/gitea/issues/13984#issuecomment-749275922
We'd want each ssh key to be a different element of an array stored in the attribute, and UI to add/remove elements in that array.
comment:3 by , 3 years ago
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
This is now fixed with https://git.osgeo.org/gitea/sac/web-cgi-bin/commit/02550ef08792a2615d170d883e3683f5cedce431
We'll store ssh keys as multiple ones (separated by newlines in the textarea)
Note:
See TracTickets
for help on using tickets.
Revision seems needed for #2457 completion (use keys with Gitea)