eclipse-ee4j / eclipse-ee4j/metro-wsit

Use of DisableStreamingSecurity in policy results in invalid ValueType for KeyIdentifier in SecurityTokenReference for STR-Transform in Sender-Vouches SAML case scenario

Open
#358 0 comments 0 reactions 0 assignees View on GitHub
3_1_2-exclude ERR: Assignee metro2_2-waived metro2_3-waived Priority: Major Type: Bug
Dominant language
Java
Stars
6
Forks
21
Avg merge
10h 2m
Merged PRs (30d)
1

Description

Client policy:

Server policy snipet:

--------------------------------
Resulting invalid SecurityTokenReference using SAML token profile 1.0 with SAMLAssertionID in a ValueType for the KeyIdentifier:

uuid-bf24cc6e-ec15-46be-9ae4-197cdd43dd50

While, it should be using SAML token profile 1.1 with SAMLID in ValueType for the KeyIdentifier in SecurityTokenReference as follows:

uuid-7fb70658-de16-4b07-b93c-e3ad1704e641

#### Environment
Ubuntu, Service - Glassfish 3.1.1 , Client Metro 2.1.1
#### Affected Versions
[2.1]

Source: [https://github.com/javaee/metro-wsit/issues/1593](https://github.com/javaee/metro-wsit/issues/1593)
Author: glassfishrobot

Contributor guide

Open the contributing guide

Research direction

Start by reproducing the client and server policy scenario on Ubuntu with Glassfish 3.1.1 and Metro 2.1.1, then inspect how the SecurityTokenReference is generated for the STR-Transform sender-vouches case. Done means the reference uses the SAML token profile 1.1 SAMLID ValueType rather than the profile 1.0 SAMLAssertionID ValueType.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
security
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.