By default, changesets can be pushed to a repository without a signature.\nWith the Signature Check plugin, this can be prevented so that only signed changesets can be pushed.
\nThe specific behavior of the signature check can be set at global, namespace and repository level.\nInitially, only the global setting is active.\nHowever, the namespace settings can explicitly override the global setting.\nIn this case, the namespace setting is active instead of the global setting.\nSimilarly, the repository setting can overwrite the global and namespace setting.\nWhen overwriting, the settings are not merged, instead only the now active setting is applied.
\nTo prevent overwriting, you can explicitly disable all repository settings in the namespace setting.\nThis will disable the settings for all repositories that belong to that namespace.\nThis applies even if the repository setting overrides the namespace setting.\nSimilarly, you can explicitly disable all namespace and repository settings in the global setting.\nThis would make only the global setting active.
\nIn order to open the global setting, one should open the Administration page via the primary navigation.\nAnd then navigate via the secondary navigation to Settings and the subitem Signature Check.\nIf the corresponding options are not available in the navigation, then the required permissions are missing.
In the global setting, one can first specify via checkbox whether the namespace and repository settings should be explicitly disabled.\nNext, you can use a checkbox to enable the feature to check every changeset for a valid signature.\nAs soon as the check is activated, further options become visible to the user.
\nThis allows the user to specify via chip input which branches should be protected from unsigned changesets during a push.\nIf the chip input is empty, then all branches are protected.\nOtherwise, only the specified branches are protected.
\nNext, the user can specify via radio buttons which gpg signatures are allowed.\nEither any signatures can be allowed or it must be the signature of an SCM manager user.\nIf any signatures are allowed and the used public key of a signature is known to the SCM manager,\nthen the signature must also match the content of the respective changeset, otherwise the push with this changeset will be rejected.\nIf the public key is not known, it is not possible to check whether the signature is correct.\nIn this case it is sufficient if the changeset has a signature.\nIf only signatures of SCM Manager users are allowed, then a check is made for each signature,\nwhether the public key belongs to a user and whether the signature matches the changeset.\nOtherwise, the push would be rejected with the respective changeset.
\nFinally, the user has to save his settings with the Save button.
To open the namespace setting you first have to go to the Repositories page via the primary navigation.\nHere you can see an overview of all namespaces and the repositories they contain.\nNext to each namespace there is a button to open the page with the settings for that namespace.\nOn this page you can open the Signature Check settings via the secondary navigation.\nIf the corresponding options are not available in the navigation, then the required permissions are missing or the namespace setting has been disabled globally.
In the namespace setting, you can use a checkbox to first specify whether the global setting should be overwritten.\nThis would only affect the respective namespace.\nAs soon as the global setting is set to be overwritten, further setting options are shown to the user.\nThe next setting allows the user to specify via checkbox whether the repository settings should be explicitly disabled.\nThis would only affect the repositories that are located in the respective namespace.\nThe subsequent setting options are analogical to the global setting.
\nTo open the repository setting you first have to go to the Repositories page via the primary navigation.\nHere you can see an overview of all namespaces and the repositories they contain.\nThen you have to click on the repository you want to configure, this will open the page of the repository.\nWith the secondary navigation and the subitem Signature Check in the tab Settings the repository setting can be opened.\nIf the corresponding options are not present in the navigation, then the required permissions are missing or the repository setting has been disabled globally or by namespace.
First, the user can use a checkbox to specify whether the settings from this repository should override the global and respective namespace setting.\nIn case of an override, further setting options are displayed analogical to the global setting.
\nTo read or change the settings it needs the respective permissions.\nFor the global setting at least the Administer permissions and the Modifiy signature check configuration permissions are required.\nFor the namespace setting, the Read permissions on namespaces permission must exist globally and the configurate signature check permission must exist for the respective namespace.\nFor the repository setting, the same permissions as for the namespace setting must be assigned at namespace or repository level.