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.

Sign up for GitHub

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

Jump to bottom

Federation Configuration File #14

Open
SchulzeStTSI opened this issue Jan 20, 2022 · 0 comments
Open

Federation Configuration File #14

SchulzeStTSI opened this issue Jan 20, 2022 · 0 comments
Labels
enhancement New feature or request Prio3
Milestone
Federation Enhanc...

Comments

@SchulzeStTSI
Copy link
Collaborator

SchulzeStTSI commented Jan 20, 2022 •
edited
Loading

Each gateway must contain one json configuration with the content of federationID, operational contact, version and the owner of the gateway, which is signed by the federation key. This configuration must be returned by a /federation/metadata route. The metadata should be signed either as CMS or as JWT (but it must embeddable later in other routes).
@SchulzeStTSI SchulzeStTSI added the enhancement New feature or request label Jan 20, 2022
@SchulzeStTSI SchulzeStTSI added this to the Federation Enhancement milestone Jan 20, 2022
@SchulzeStTSI SchulzeStTSI changed the title Secure Federation Configuration Federation Configuration File Jan 20, 2022
@f11h f11h mentioned this issue Mar 9, 2022
Closed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request Prio3
Projects
None yet
Milestone
Federation Enhancement
Development

No branches or pull requests
2 participants
@ascheibal @SchulzeStTSI