Skip to content

feat: manage certificate policy #4833

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
Merged
merged 15 commits into from
May 17, 2025
Merged

feat: manage certificate policy #4833

merged 15 commits into from
May 17, 2025

Conversation

vitormattos
Copy link
Member

@vitormattos vitormattos commented Apr 11, 2025 •
edited
Loading

At Administration Settings > LibreSign

Before generate certificate:

image

After generate certificate:

image

Reading certificate data is possible to see the certificate policies at owner and issuer certificate:
image

How to see this running using GitHub Codespaces

1. Open the Codespace

  • Authenticate to GitHub
  • Go to the branch: feat/manage-certificate-policy
  • Click the Code button and select the Codespaces tab.
  • Click "Create codespace on feat/customize-signature-stamp"

2. Wait for the environment to start

  • A progress bar will appear on the left.
  • After that, the terminal will show the build process.
  • Wait until you see the message: 
    ✍️ LibreSign is up!
    This may take a few minutes.

3. Access LibreSign in the browser

  • Open the Ports tab (next to the Terminal).
  • Look for the service running on port 80.
  • Hover over the URL and click the globe icon 🌐 to open it in your browser.

4. (Optional) Make the service public

  • If you want to share the app with people not logged in to GitHub, you must change the port visibility:
    • Click the three dots ⋮ on the row for port 80.
    • Select Change visibility → Public.

5. Login credentials

  • Username: admin
  • Password: admin

Done! 🎉
You're now ready to test this.

@vitormattos vitormattos added this to the Next Major (32) milestone Apr 11, 2025
@vitormattos vitormattos self-assigned this Apr 11, 2025
@github-project-automation github-project-automation bot moved this to 0. Needs triage in Roadmap Apr 11, 2025
@vitormattos vitormattos marked this pull request as draft April 11, 2025 20:31
@vitormattos vitormattos force-pushed the feat/manage-certificate-policy branch 2 times, most recently from e9409ac to 17b8605 Compare April 12, 2025 15:22
@vitormattos
feat: manage certificate policy
9d1060b 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos vitormattos force-pushed the feat/manage-certificate-policy branch 8 times, most recently from a197b6c to 7b5991e Compare April 16, 2025 19:45
@vitormattos
chore: Implement administration settings of Certificate Policy
2c95807 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
feat: implement changes at backend to support Certificate Policy
f397fb7 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
chore: reduce regex to be more readdable by sysadmin
02f46d1 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos vitormattos force-pushed the feat/manage-certificate-policy branch from 7b5991e to 8147983 Compare April 17, 2025 01:48
@vitormattos
chore: move CertificatePolocy to root cert flow
1bde1bd 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
fix: constructor methods need to use the same attributes
8842350 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos vitormattos force-pushed the feat/manage-certificate-policy branch from 8147983 to 8842350 Compare April 17, 2025 02:00
@vitormattos
fix: generate directory recursive when receive the path from frontend
e2fd622 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
fix: add events
66094a9 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
fix: prevent error when directory already exists
03b36b2 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
fix: replace vitual file system by temp folder
9c67151 
The openssl extension don't work fine with virtual file system

Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos vitormattos force-pushed the feat/manage-certificate-policy branch from e3fde53 to 9c67151 Compare April 17, 2025 12:17
@vitormattos
fix: unit test
902d31a 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
chore: rename URL to CPS and return this at get certificate details e…
b507df9 
…ndpoint

Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos
chore: change URL to CPS
6f32e6a 
CPS is the right name of this

Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos vitormattos force-pushed the feat/manage-certificate-policy branch from 57dee84 to 9992864 Compare April 17, 2025 18:28
@vitormattos
fix: documentation
d7e3e59 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos vitormattos force-pushed the feat/manage-certificate-policy branch from 9992864 to d7e3e59 Compare April 17, 2025 18:30
@vitormattos
chore: cover with unit tests
7e39a4e 
Signed-off-by: Vitor Mattos <vitor@php.rio>
@vitormattos vitormattos force-pushed the feat/manage-certificate-policy branch from 77cf348 to 7e39a4e Compare April 18, 2025 13:23
@vitormattos vitormattos marked this pull request as ready for review April 18, 2025 13:27
@vitormattos
Copy link
Member Author

/backport to stable31

@vitormattos
Copy link
Member Author

/backport to stable30

@samuelsonbrito samuelsonbrito merged commit 4393450 into main May 17, 2025
83 of 94 checks passed
@samuelsonbrito samuelsonbrito deleted the feat/manage-certificate-policy branch May 17, 2025 03:14
@github-project-automation github-project-automation bot moved this from 0. Needs triage to 4. to release in Roadmap May 17, 2025
This was referenced May 17, 2025
Merged
Merged
@vitormattos vitormattos removed this from the Next Major (32) milestone May 20, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers

@samuelsonbrito samuelsonbrito Awaiting requested review from samuelsonbrito

Assignees

@vitormattos vitormattos

Labels
None yet
Projects
Roadmap
Status: 4. to release
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
2 participants
@vitormattos @samuelsonbrito