OpenConext / OpenConext/Mujina

How do I enable encryption for the SAML Assertion

Open
#74 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

stale
Dominant language
Java
Stars
386
Forks
172
Avg merge
3d 18h
Merged PRs (30d)
6

Description

I use Mujina to serve as IDP, but the SP require encryption for the SAML assertion. The metadata of the SP contain "encryption":

<md:KeyDescriptor use="encryption"><ds:KeyInfo xmlns:ds="http://www.w3.org/2000/09/xmldsig#"><ds:X509Data><ds:X509Certif
icate>MIIEAzCCAuugAwIBAgIUI4qKN939RQDNUu/xfdzQXYmMfuowDQYJKoZIhvcNAQELBQAwgZAxCzAJ
BgNVBAYTAlRXMQ8wDQYDVQQIDAZUYWl3YW4xETAPBgNVBAcMCFRhbyBZdWFuMSQwIgYDVQQKDBtO
...

Will it possibly work with Mujina IDP? And how should I do to make the it work.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

No source files or tests are named. Start by tracing how Mujina's IDP creates SAML assertions and reviewing the OpenSAML support for encrypting them with the certificate from the SP metadata; done means an SP requiring assertion encryption accepts the resulting response.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
authentication, security
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.