Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[8.0] IAM2CS: ForceNickname, fix duplicate accounts for users #7784

Merged
merged 6 commits into from
Sep 17, 2024

Commits on Sep 11, 2024

  1. feat(VOMS2CSAgent): add ForceNickname option to only add users where …

    …a nickname attribute is defined
    andresailer committed Sep 11, 2024
    Configuration menu
    Copy the full SHA
    0574c0c View commit details
    Browse the repository at this point in the history
  2. fix(VOMS2CSAgent): do not change the username if a nickname is defined

    When there are multiple VOs where a user is present and there are multiple Certificates multiple dirac accounts where created for that user.
    Now the nickname is always used and no index is added with new users
    andresailer committed Sep 11, 2024
    Configuration menu
    Copy the full SHA
    6773c43 View commit details
    Browse the repository at this point in the history
  3. feat(IAMService): use logger, return errors for getUser function and …

    …log them to VOMS2CSAgent email
    andresailer committed Sep 11, 2024
    Configuration menu
    Copy the full SHA
    fdce07a View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    c4b4bc4 View commit details
    Browse the repository at this point in the history
  5. Configuration menu
    Copy the full SHA
    183c1d4 View commit details
    Browse the repository at this point in the history

Commits on Sep 13, 2024

  1. Configuration menu
    Copy the full SHA
    e6c5eea View commit details
    Browse the repository at this point in the history