Ecosyste.ms: Awesome
An open API service indexing awesome lists of open source software.
https://github.com/barbarpotato/coretify-x
A Custom Personal Coretify that has Personal Functionality for adapting necessary needs for Personal Project Architecture
https://github.com/barbarpotato/coretify-x
authentication bootstrap bun express htmx javascript jwt mysql prisma rate-limiter redis
Last synced: 9 days ago
JSON representation
A Custom Personal Coretify that has Personal Functionality for adapting necessary needs for Personal Project Architecture
- Host: GitHub
- URL: https://github.com/barbarpotato/coretify-x
- Owner: Barbarpotato
- License: unlicense
- Created: 2024-09-21T10:39:24.000Z (4 months ago)
- Default Branch: main
- Last Pushed: 2024-12-29T04:29:04.000Z (11 days ago)
- Last Synced: 2024-12-29T05:21:19.101Z (11 days ago)
- Topics: authentication, bootstrap, bun, express, htmx, javascript, jwt, mysql, prisma, rate-limiter, redis
- Language: EJS
- Homepage: https://coretify.vercel.app
- Size: 285 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# Coretify X
The Personal Coretify Version that used for privacy needs, Such as creating Proxy between client and backend server. It Contains Tricky algorithm about how transfering data works like hashing, encryption, decryption and a secret key.## Proxy Route
- The client sends an initial request to the proxy (Coretify). This request does not include any sensitive tokens, ensuring secure interaction from the client side.
- The proxy generates a signed JWT token and sends it back to the client. This token serves as a temporary authentication mechanism.
- The client sends a new request to the Site Registry (CDN) and includes the JWT token received from the proxy in the request header.
- The Site Registry verifies the JWT token by forwarding it to the proxy. The proxy acts as a validator to confirm the token’s validity.
- If the proxy validates the JWT token, it grants access to the requested resource on the Site Registry. The requested data is then sent back to the client through the proxy.