Merge branch 'main' into snyk-upgrade-f08831b04651b2004346211d021c98b6

.github/CODEOWNERS

@@ -8,6 +8,8 @@
 /automation/ @moabu
 /charts/ @moabu
 /.github/ @moabu
+/jans-*/version.txt @moabu
+/jans-*/CHANGELOG.md @moabu
 /jans-pycloudlib/ @moabu
 /docker-jans-*/requirments.txt @mo-auto
 /jans-bom/ @yurem @yuriyz
@@ -18,7 +20,9 @@
 /jans-auth-server/ @yurem @yuriyz
 /jans-fido2/ @yurem
 /jans-scim/ @jgomer2001
-/jans-client-api/ @duttarnab @yuriyz
-/jans-config-api/ @pujavs @yuriyz
-/jans-cli/ @mbaser
-/jans-ce-setup/ @mbaser @smansoft
+/jans-config-api/ @pujavs @yuriyz @yurem
+/jans-cli-tui/ @devrimyatar
+/jans-linux-setup/ @devrimyatar @smansoft @yuriyz @yurem
+/jans-linux-setup/jans_setup/setup_app/version.py @moabu
+/jans-linux-setup/static/scripts/admin_ui_plugin.py @devrimyatar @duttarnab
+/agama/ @jgomer2001

.github/ISSUE_TEMPLATE/development-item.md

@@ -0,0 +1,61 @@
+---
+name: Development item
+about: Create this issue if you are a developer who is contributing code for a feature or bug, and you want to track or co-ordinate development work
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+<!-- 
+If a section or line item is not applicable, please put `NA` at the end of the line 
+We recommend tracking each non-trivial task as separate issue. 
+To quickly do that,
+- list your task titles in the list below (it'll become title of the issue later)
+- after you submit this issue, you can quickly create issues for each task below from description of this issue.
+Refer to the link below for help.
+(https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue#creating-an-issue-from-a-task-list-item)
+-->
+
+-------------------
+
+### Description
+
+- Development target issue
+  <!-- Mention original Github `feature request` or `bug` ID which is being addressed -->
+
+- Implementation Details
+  <!-- Communicate high level analysis and implementation approach -->
+
+-------------------
+
+### Prepare
+
+- [ ] Read contribution guidelines
+- [ ] Read license information
+
+------------------
+
+### Identified code changes
+
+
+- [ ] task 1
+- [ ] task 2
+- [ ] task 3
+
+-------------------
+
+### Test cases and code coverage
+
+- [ ] Write unit test to cover added/changed code
+- [ ] Update integration tests to cover added/changed code
+
+-------------------
+
+### Document the changes
+
+- [ ] task for updating user guides if needed
+- [ ] task for updating installation and configuration guides if needed 
+- [ ] task for updating developer documentation if needed
+- [ ] task for updating technical documentation if needed
+

.github/ISSUE_TEMPLATE/failing-tests.md

@@ -0,0 +1,20 @@
+---
+name: Failing tests
+about: You noticed a flaky test or a problem with a build? This is the kind of issue to triage that!
+title: ''
+labels: ''
+assignees: ''
+
+---
+
+### What is failing?
+<!-- Mention the type of failure like build, test etc -->
+
+### Where is it failing?
+<!-- Mention the environment where you are seeing the failure. If possible, give the link where failure can be seen. e.g Link to Jenkins build -->
+
+### Relevent logs
+<!-- Paste relevent logs if you have any -->
+
+### Possible root cause
+<!-- Mention if you have a guess about what may be causing this failure. -->

.github/SECURITY.md

@@ -0,0 +1,24 @@
+# Security Policy
+
+The **JanssenProject** team and community take security bugs seriously.
+
+We appreciate your efforts to responsibly disclose your findings, and will make every effort to acknowledge your contributions.
+
+## Supported versions
+
+Security updates will typically only be applied to the latest release (at least until **Janssen** reaches first stable major version).
+
+| Version  | Supported          |
+| -------- | ------------------ |
+| >=0.1 | :white_check_mark: |
+
+## Reporting a vulnerability
+
+To report a security issue, send an email to [security@jans.io](mailto:security@jans.io?subject=SECURITY)
+
+The **Janssen** team will send a response indicating the next steps in handling your report.
+After the initial reply to your report, the team will keep you informed of the progress towards a fix and full announcement,
+and may ask for additional information or guidance.
+
+Note also that the team can use [GitHub Security Advisories](https://help.github.com/en/github/managing-security-vulnerabilities/about-github-security-advisories)
+to disclose, fix, and publish information about the vulnerability you responsibly reported to us.

.github/pull_request_template.md

@@ -0,0 +1,25 @@
+### Prepare
+
+- [ ] Read [PR guidelines](https://github.com/JanssenProject/jans/blob/main/docs/CONTRIBUTING.md#prs)
+- [ ] Read [license information](https://github.com/JanssenProject/jans/blob/main/LICENSE)
+
+-------------------
+
+### Description
+
+#### Target issue
+  <!-- Link or describe the issue this PR is fixing -->
+
+  <!-- If issue shouldn't be closed after merging this PR, then we recommend adding a task in original target issue and create a separate issue from this task which can be closed when this PR gets merged. Mention this new issue created from task as target issue below. For more on how to create task issues visit https://docs.github.com/en/issues/tracking-your-work-with-issues/about-task-lists -->
+
+closes #issue-number-here
+
+#### Implementation Details
+  <!-- If the fix is an involved one then communicate high level analysis and implementation approach -->
+
+-------------------
+### Test and Document the changes
+- [ ] Static code analysis has been run locally and issues have been fixed
+- [ ] Relevant unit and integration tests have been added/updated
+- [ ] Relevant documentation has been updated if any (i.e. user guides, installation and configuration guides, technical design docs etc)
+

.github/workflows/backport.yml

@@ -0,0 +1,52 @@
+name: Backport
+on:
+  pull_request_target:
+    types: [closed, labeled]
+    branches: [main, release-*]
+
+# WARNING:
+# When extending this action, be aware that $GITHUB_TOKEN allows write access to
+# the GitHub repository. This means that it should not evaluate user input in a
+# way that allows code injection.
+
+jobs:
+  backport:
+    name: Backport Pull Request
+    # Run the action if a PR is merged with backport labels
+    # OR
+    # when already merged PR is labeled with backport labels
+    if: >
+      github.event.pull_request.merged
+      && (
+        github.event.action == 'closed'
+        || (
+          github.event.action == 'labeled'
+          && startsWith(github.event.label.name, 'backport/')
+        )
+      )
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v3
+        with:
+          # required to find all branches
+          fetch-depth: 0
+          token: ${{ secrets.MOAUTO_WORKFLOW_TOKEN }}
+          ref: ${{ github.event.pull_request.head.sha }}
+      - name: Create backport PRs
+        # should be kept in sync with `version`
+        uses: zeebe-io/backport-action@v1.0.1
+        with:
+          # Config README: https://github.com/zeebe-io/backport-action#backport-action
+          github_token: ${{ secrets.MOAUTO_WORKFLOW_TOKEN }}
+          github_workspace: ${{ github.workspace }}
+          # should be kept in sync with `uses`
+          version: v0.0.8
+
+          # Regex pattern to match GitHub labels
+          # The capture group catches the target branch
+          # i.e. label backport/v1.0.0 will create backport PR for branch v1.0.0
+          label_pattern: ^backport\/([^ ]+)$
+
+          pull_description: |-
+            Automated backport to `${target_branch}`, triggered by a label in #${pull_number}.
+            See ${issue_refs}.