Skip to content

Commit 6d9ffa2

Browse files
push2085push2085
committed
Organizing the existing FIDO2 code in the new repository format
1 parent cf403a4 commit 6d9ffa2

File tree

425 files changed

+59549
-2
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

425 files changed

+59549
-2
lines changed

‎.github/ISSUE_TEMPLATE/bug_report.md

+38
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,38 @@
1+
---
2+
name: Bug report
3+
about: Create a report to help us improve
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Describe the bug**
11+
A clear and concise description of what the bug is.
12+
13+
**To Reproduce**
14+
Steps to reproduce the behavior:
15+
1. Go to '...'
16+
2. Click on '....'
17+
3. Scroll down to '....'
18+
4. See error
19+
20+
**Expected behavior**
21+
A clear and concise description of what you expected to happen.
22+
23+
**Screenshots**
24+
If applicable, add screenshots to help explain your problem.
25+
26+
**Desktop (please complete the following information):**
27+
- OS: [e.g. iOS]
28+
- Browser [e.g. chrome, safari]
29+
- Version [e.g. 22]
30+
31+
**Smartphone (please complete the following information):**
32+
- Device: [e.g. iPhone6]
33+
- OS: [e.g. iOS8.1]
34+
- Browser [e.g. stock browser, safari]
35+
- Version [e.g. 22]
36+
37+
**Additional context**
38+
Add any other context about the problem here.

‎.github/ISSUE_TEMPLATE/feature_request.md

+20
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,20 @@
1+
---
2+
name: Feature request
3+
about: Suggest an idea for this project
4+
title: ''
5+
labels: ''
6+
assignees: ''
7+
8+
---
9+
10+
**Is your feature request related to a problem? Please describe.**
11+
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
12+
13+
**Describe the solution you would like**
14+
A clear and concise description of what you want to happen.
15+
16+
**Describe alternatives you have considered**
17+
A clear and concise description of any alternative solutions or features you've considered.
18+
19+
**Additional context**
20+
Add any other context or screenshots about the feature request here.

‎.gitignore

+22
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,22 @@
1+
_site/
2+
.sass-cache/
3+
.jekyll-cache/
4+
.jekyll-metadata
5+
fidoserver/.DS_store
6+
fidoserver/keymanager/target/
7+
fidoserver/fidoserverEAR/target/
8+
fidoserver/fido2mds/src/main/resources/authenticator/metadata/GoTrust_Secp256R1_FIDO2_Interop_CTAP2_Authenticator_newer.json
9+
fidoserver/fido2mds/src/main/resources/authenticator/metadata/CTAP2Secp256r1AttCert.metadata.json
10+
fidoserver/fido2mds/src/main/resources/authenticator/metadata/KONAI_MDS_1.json
11+
fidoserver/fido2mds/src/main/resources/authenticator/metadata/eSecu_FIDO2_Metadata.json
12+
fidoserver/fido2mds/src/main/resources/authenticator/metadata/feitian-AllinOneFIDO2_USB_BLE_NFC.json
13+
fidoserver/fido2mds/src/main/resources/authenticator/metadata/feitian-BioFIDO2_USB_withCN.json
14+
fidoserver/fido2mds/src/main/resources/authenticator/metadata/feitian-ePassFIDO2_USB.json
15+
server/api/target/
16+
server/authenticationBeans/target/
17+
server/common/target/
18+
server/crypto/target/
19+
server/fido2mds/target/
20+
server/fidoserverEAR/target/
21+
server/fidoserverbeans/target/
22+
/sampleapps/java/basic/server/target/

‎CODE_OF_CONDUCT.md

+76
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,76 @@
1+
# Contributor Covenant Code of Conduct
2+
3+
## Our Pledge
4+
5+
In the interest of fostering an open and welcoming environment, we as
6+
contributors and maintainers pledge to making participation in our project and
7+
our community a harassment-free experience for everyone, regardless of age, body
8+
size, disability, ethnicity, sex characteristics, gender identity and expression,
9+
level of experience, education, socio-economic status, nationality, personal
10+
appearance, race, religion, or sexual identity and orientation.
11+
12+
## Our Standards
13+
14+
Examples of behavior that contributes to creating a positive environment
15+
include:
16+
17+
* Using welcoming and inclusive language
18+
* Being respectful of differing viewpoints and experiences
19+
* Gracefully accepting constructive criticism
20+
* Focusing on what is best for the community
21+
* Showing empathy towards other community members
22+
23+
Examples of unacceptable behavior by participants include:
24+
25+
* The use of sexualized language or imagery and unwelcome sexual attention or
26+
advances
27+
* Trolling, insulting/derogatory comments, and personal or political attacks
28+
* Public or private harassment
29+
* Publishing others' private information, such as a physical or electronic
30+
address, without explicit permission
31+
* Other conduct which could reasonably be considered inappropriate in a
32+
professional setting
33+
34+
## Our Responsibilities
35+
36+
Project maintainers are responsible for clarifying the standards of acceptable
37+
behavior and are expected to take appropriate and fair corrective action in
38+
response to any instances of unacceptable behavior.
39+
40+
Project maintainers have the right and responsibility to remove, edit, or
41+
reject comments, commits, code, wiki edits, issues, and other contributions
42+
that are not aligned to this Code of Conduct, or to ban temporarily or
43+
permanently any contributor for other behaviors that they deem inappropriate,
44+
threatening, offensive, or harmful.
45+
46+
## Scope
47+
48+
This Code of Conduct applies both within project spaces and in public spaces
49+
when an individual is representing the project or its community. Examples of
50+
representing a project or community include using an official project e-mail
51+
address, posting via an official social media account, or acting as an appointed
52+
representative at an online or offline event. Representation of a project may be
53+
further defined and clarified by project maintainers.
54+
55+
## Enforcement
56+
57+
Instances of abusive, harassing, or otherwise unacceptable behavior may be
58+
reported by contacting the project team at [email protected]. All
59+
complaints will be reviewed and investigated and will result in a response that
60+
is deemed necessary and appropriate to the circumstances. The project team is
61+
obligated to maintain confidentiality with regard to the reporter of an incident.
62+
Further details of specific enforcement policies may be posted separately.
63+
64+
Project maintainers who do not follow or enforce the Code of Conduct in good
65+
faith may face temporary or permanent repercussions as determined by other
66+
members of the project's leadership.
67+
68+
## Attribution
69+
70+
This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 1.4,
71+
available at https://www.contributor-covenant.org/version/1/4/code-of-conduct.html
72+
73+
[homepage]: https://www.contributor-covenant.org
74+
75+
For answers to common questions about this code of conduct, see
76+
https://www.contributor-covenant.org/faq

‎CONTRIBUTING.md

+50
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,50 @@
1+
# Contributing to StrongKey's FIDO2 Server
2+
3+
We welcome contributions to this open-source FIDO2 Server! This guide provides some tips for successful contributions.
4+
5+
For some background on WebAuthn/FIDO2 and its backers, visit the [FIDO2 Project](https://fidoalliance.org/fido2/).
6+
7+
For complex changes, we recommend filing a GitHub Issue to start a discussion with project maintainers before implementing the change.
8+
9+
## Pull Requests
10+
11+
Please make sure the following is done when submitting a Pull Request:
12+
13+
1. Fork the repo and create your branch from `master`.
14+
2. If you've added code that should be tested, add unit test code.
15+
3. If you've changed APIs, update the .YAML documentation files.
16+
4. Ensure your test suite passes.
17+
5. If you haven't already, complete the Contributor License Agreement (CLA), linked below.
18+
6. Submit your Pull Request through GitHub.
19+
20+
## Contributor License Agreement (CLA)
21+
22+
You must sign a CLA before your Pull Request will be merged. This is a one-time requirement for StrongKey open-source projects in GitHub. You can read more about [Contribution License Agreements](https://en.wikipedia.org/wiki/Contributor_License_Agreement) on Wikipedia.
23+
24+
Follow this link to sign the StrongKey [Contributor License Agreement (CLA)](https://cla-assistant.io/StrongKey/FIDO-Server).
25+
26+
## Issues and New Features
27+
28+
We use GitHub [Issues](../../issues) to track bugs and feature additions.
29+
30+
### Did you discover a bug?
31+
32+
Do not open up a GitHub Issue if the bug is a security vulnerability in FIDO2 Server, and instead email [[email protected]](mailto:[email protected]).
33+
34+
Ensure the bug was not already reported by searching on GitHub Issues.
35+
36+
If you're unable to find an open issue addressing the problem, open a new one. Be sure to include a title and clear description, as much relevant information as possible, and a code sample or an executable test case demonstrating the expected behavior that is not occurring.
37+
38+
Please use GitHub [Issues](../../issues) to create the Bug Report. Click NEW ISSUE, then GET STARTED in the row labeled BUG REPORT, then complete the form.
39+
40+
### Did you write a patch that fixes a bug (including documentation)?
41+
42+
Open a new GitHub Pull Request with the patch.
43+
44+
Ensure the Pull Request description clearly describes the problem and solution. Include the relevant issue number if applicable.
45+
46+
### Do you intend to add a new feature or change an existing one (including documentation)?
47+
48+
Submit a Feature Request with your change using GitHub [Issues](../../issues). Click NEW ISSUE, then GET STARTED in the row labeled FEATURE REQUEST, completing the form; then start writing code.
49+
50+
Do not open a Feature Request on GitHub until you have collected positive feedback about the change. GitHub issues are primarily intended for Bug Reports and fixes.

0 commit comments

Comments
 (0)