Add SSH keys on login from LDAP #2663

Closed
opened 2025-11-02 04:43:50 -06:00 by GiteaMirror · 3 comments
Owner

Originally created by @NomAnor on GitHub (Dec 14, 2018).

  • Gitea version (or commit ref): master
  • Git version: 2.20.0
  • Operating system: Arch Linux
  • Database (use [x]):
    • PostgreSQL
    • MySQL
    • MSSQL
    • SQLite
  • Can you reproduce the bug at https://try.gitea.io:
    • Yes (provide example URL)
    • No
    • Not relevant
  • Log gist:

Description

The SSH keys in the LDAP directory are only added to the user accounts when the synchronization task is run not when a user first logs in.

This means that a user can't push as soon as he is logged in and he needs to add the key himself making the key storage in LDAP not so useful.

Is it possible to add the keys when the user is created on first login?

Originally created by @NomAnor on GitHub (Dec 14, 2018). - Gitea version (or commit ref): master - Git version: 2.20.0 - Operating system: Arch Linux - Database (use `[x]`): - [ ] PostgreSQL - [ ] MySQL - [ ] MSSQL - [x] SQLite - Can you reproduce the bug at https://try.gitea.io: - [ ] Yes (provide example URL) - [ ] No - [x] Not relevant - Log gist: ## Description The SSH keys in the LDAP directory are only added to the user accounts when the synchronization task is run not when a user first logs in. This means that a user can't push as soon as he is logged in and he needs to add the key himself making the key storage in LDAP not so useful. Is it possible to add the keys when the user is created on first login?
GiteaMirror added the type/enhancement label 2025-11-02 04:43:50 -06:00
Author
Owner

@zeripath commented on GitHub (Dec 17, 2018):

Hi @NomAnor I wonder if you could test #5557 and see if that fixes your issue?

@zeripath commented on GitHub (Dec 17, 2018): Hi @NomAnor I wonder if you could test #5557 and see if that fixes your issue?
Author
Owner

@zeripath commented on GitHub (Jan 2, 2019):

@NomAnor, #5557 has been merged into the master branch. Does that solve your issue? If so, could you close this.

@zeripath commented on GitHub (Jan 2, 2019): @NomAnor, #5557 has been merged into the master branch. Does that solve your issue? If so, could you close this.
Author
Owner

@lafriks commented on GitHub (Jan 5, 2019):

Closing as fixed

@lafriks commented on GitHub (Jan 5, 2019): Closing as fixed
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#2663