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

createToken.py: Allow specification of the JWT key file and output file #676

Merged
merged 1 commit into from
Mar 1, 2024

Commits on Feb 29, 2024

  1. createToken.py: Allow specification of the JWT key file and output file

    Current version of the script assumes that jwt key file is located in
    the same directory as the script itself and token is written into the
    same directory as json specification. This is not convinient for binary
    distribution with key files placed under /etc and script under bin or
    libexec dirs.
    Allowing specification of key file and output files location fixes this
    and application token can be generated with [1] while keeping backward
    compatibility and existing behaviour (single argument to specify json
    policy definition)
    Error out if both output option and multiple input files have been
    specified
    
    [1]
    /usr/libexec/kuksa-createToken.py /usr/share/kuksa-val/jwt/all-read-write.json --key /etc/pki/kuksa/jwt.key --output /etc/xdg/AGL/%i/%i.token
    landgraf committed Feb 29, 2024
    Configuration menu
    Copy the full SHA
    bd97386 View commit details
    Browse the repository at this point in the history