Skip to content

ISSUE #158: JWKS Authentication and API Gateway#150

Open
chazapp wants to merge 21 commits into
mainfrom
jwks-gateway
Open

ISSUE #158: JWKS Authentication and API Gateway#150
chazapp wants to merge 21 commits into
mainfrom
jwks-gateway

Conversation

@chazapp

@chazapp chazapp commented Mar 15, 2025

Copy link
Copy Markdown
Collaborator

This PR finishes implementation of JWKS based authentication. The ea-front project emits JWTs that can be verified using the public key accessible at /api/jwks ; The PR also configures the Istio API Gateway to access the front-end over HTTP and HTTPS via self-signed certificate.

@im-knots im-knots changed the title feat: JWKS Authentication and API Gateway ISSUE #158: JWKS Authentication and API Gateway Mar 17, 2025
@im-knots

Copy link
Copy Markdown
Owner

Problem right now:

no header curl request yields RBAC: access is denied
header with valid jwt from frontend gives Jwt issuer is not configured

@im-knots

Copy link
Copy Markdown
Owner

got it working with the above commit. we need to include the iss and sub fields and match iss to the issuer field on the kind: RequestAuthentication

const privateKey = await getPrivateKey();
const token = await new jose.SignJWT({
email: userRecord.email,
iss: "eru-labs-jwt-issuer",

Copy link
Copy Markdown
Collaborator Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
iss: "eru-labs-jwt-issuer",
iss: "eru-labs",

It's the brand signature, no need to be explicit about jwt-issuer

@im-knots

Copy link
Copy Markdown
Owner

I updated the agent-manager (typo in commit) give it a look over when you get a chance. i think i did it correctly. Im going to work on the agent-builder and settings page next.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants