Re: [Id-event] SAML subject identifier type

Atul Tulshibagwale <atultulshi@google.com> Mon, 13 July 2020 20:22 UTC

Return-Path: <atultulshi@google.com>
X-Original-To: id-event@ietfa.amsl.com
Delivered-To: id-event@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 05F483A0C8E for <id-event@ietfa.amsl.com>; Mon, 13 Jul 2020 13:22:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -17.599
X-Spam-Level:
X-Spam-Status: No, score=-17.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIMWL_WL_MED=-0.001, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, ENV_AND_HDR_SPF_MATCH=-0.5, HTML_MESSAGE=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001, USER_IN_DEF_DKIM_WL=-7.5, USER_IN_DEF_SPF_WL=-7.5] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=google.com
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id vW3OD7Mg8J6B for <id-event@ietfa.amsl.com>; Mon, 13 Jul 2020 13:22:49 -0700 (PDT)
Received: from mail-yb1-xb31.google.com (mail-yb1-xb31.google.com [IPv6:2607:f8b0:4864:20::b31]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id F390A3A0D38 for <id-event@ietf.org>; Mon, 13 Jul 2020 13:22:15 -0700 (PDT)
Received: by mail-yb1-xb31.google.com with SMTP id y17so7042952ybm.12 for <id-event@ietf.org>; Mon, 13 Jul 2020 13:22:15 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=YO9XgLpQNX8k1hO/mw1+uTCGD2oL9osp3tFt0J6WAQ8=; b=SY5yE8rm8I58vtD12TFp6HS7bTKoGuOQ4NZZDUoHMAuI7Toz6TimT9tBmA+o0TdeUU EQRMkBzWjCBixfXdutSIb//psUEWTiuW5cdlWkLvgnmI4Z3E3P/5z0tx4whGAsmBhL0p kF5WZPaN6sLvmUlpVqWPXRAXjoYDaLLG/8NVO2KgO+7e5v0lzGzW5u6ahM4bbJoQEQHL kqhaLJF8yThxh5MyTDmCAYKRuQRHNwCD1m909U4hPlh7feSVl8UQm3iVYvILfypK5QOe RzjsHqiqt1R9BkoX25rkf/zIESf7Xp8aLAu6ncgazQbgbOCyHMfpo2Ow2iMuE6JCGaZ1 XG6Q==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=YO9XgLpQNX8k1hO/mw1+uTCGD2oL9osp3tFt0J6WAQ8=; b=qCRhrQBhMTBUw/T5SpX4b6CSqwyhuA27xqDKg7I/zHA9i8jh5TkKWvneIqhvTBvOkj yXjUzuTowBrGgdMtHcWGDcOeXBGo5Xc5MdOSMdZD1dPbps2FPxgqQfBaCgJg7PLPVqMF twEnNKP3FTgPwLMAsuI2b4wteD1SuXWnqu7G3VAlwTjDXOKLsXjAnkTMr8cyUC1FyKNY NyM9dDVFPAotFKlwGdkZzxHwFcmiDXtJfizJ81zB3GVYk5stkjt5cW0Xll8SSbawo0zC ALIKSFm5mS+Z8+RDMvhRCMdPBrmEBuq3YUZX/vursmbsXeZEwmpwdg6n7VKQUcHUEeTE FQfw==
X-Gm-Message-State: AOAM533PEZp7ytzbflSNa77DbrOEJF/bZU8QXbhyu4O69/hq5HG/Smyj 0MAHGpgBXI6yTti7MFDBopUYJbC9RKTRLZEKjErrWc6L
X-Google-Smtp-Source: ABdhPJz1hoVCMtxpdzAB6kOvVPdNlOmT9niSy8VKDmKi2vgjfnL3uIscm8iN3Tjt72jMp0VN47vIiWLmSkT94dlDI3M=
X-Received: by 2002:a25:5ac5:: with SMTP id o188mr2995873ybb.322.1594671734714; Mon, 13 Jul 2020 13:22:14 -0700 (PDT)
MIME-Version: 1.0
References: <CAMCkG5thP1JnyBn5qAK0TLqBoa-y53Qnoq=mf-NPLfzSF2U7VQ@mail.gmail.com> <5B3455F1-9F82-40C5-BE22-2E3B715A0CF1@canarie.ca>
In-Reply-To: <5B3455F1-9F82-40C5-BE22-2E3B715A0CF1@canarie.ca>
From: Atul Tulshibagwale <atultulshi@google.com>
Date: Mon, 13 Jul 2020 13:22:03 -0700
Message-ID: <CAMCkG5uSQzTGCmFn6DLeXVbA0B0wrcPou8CEjtCQ5BCp3M+eOw@mail.gmail.com>
To: Chris Phillips <Chris.Phillips@canarie.ca>
Cc: "id-event@ietf.org" <id-event@ietf.org>
Content-Type: multipart/alternative; boundary="000000000000484a3305aa5872da"
Archived-At: <https://mailarchive.ietf.org/arch/msg/id-event/55repRpNMfjhsVLOOwVrOauA5Aw>
Subject: Re: [Id-event] SAML subject identifier type
X-BeenThere: id-event@ietf.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: "A mailing list to discuss the potential solution for a common identity event messaging format and distribution system." <id-event.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/id-event>, <mailto:id-event-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/id-event/>
List-Post: <mailto:id-event@ietf.org>
List-Help: <mailto:id-event-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/id-event>, <mailto:id-event-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 13 Jul 2020 20:22:51 -0000

Hi Chris,
I was proposing using the "assertion id" (SAML Core
<http://docs.oasis-open.org/security/saml/v2.0/saml-core-2.0-os.pdf> spec,
line 553) in the proposal, not the "subject-id" as defined in SAML (spec
section 3.3). The main reason was to be able to refer to a session that was
established using a specific assertion. If it's useful, we could perhaps
extend the SAML subject identifier type in this spec to include either the
assertion_id or the subject_id claim.

Thanks,
Atul


On Mon, Jul 13, 2020 at 10:30 AM Chris Phillips <Chris.Phillips@canarie.ca>
wrote:

> Hi.
>
> Quiet lurker observing..
>
> Thanks for consider the SAML elements..
>
>
>
> Atul, are you referring to the actual session identifier that someone may
> have where the Subject-Id was exchanged OR the actual Subject-id itself in
> your reference in the proposal with the github link?
>
>
>
> I’m trying to square what I see on the git delta on line 294-296 in
> https://github.com/richanna/secevent/pull/1/commits/b20b6692eb50628927476ca78f9be077ace88994
>
>
>
>
>
> And a Subject-id as shown in the example in 3.3.3 here:
> https://docs.oasis-open.org/security/saml-subject-id-attr/v1.0/cs01/saml-subject-id-attr-v1.0-cs01.html#_Toc536097229
>
>
>
> What you offered in the example is not a Subject-id  per the OASIS SAML
> spec as written in section 3.3.1
>
>
>
> Am I mis-interpreting something?
>
>
>
> C
>
>
>
>
>
> *From: *Id-event <id-event-bounces@ietf.org> on behalf of Atul
> Tulshibagwale <atultulshi=40google.com@dmarc.ietf.org>
> *Date: *Monday, July 13, 2020 at 12:17 PM
> *To: *"id-event@ietf.org" <id-event@ietf.org>
> *Subject: *[Id-event] SAML subject identifier type
>
>
>
> Hi all,
>
> Based on the discussions in the SSE working group within the OpenID
> Foundation, we would like to propose that the subject identifier
> specification include a SAML subject identifier type. This is so that
> sessions established across peers using SAML may be identified in events
> that include the subject identifier.
>
>
>
>  A SAML subject identifier has only one claim within it, the assertion id
> of the SAML assertion used to establish the single sign-on session.
>
>
>
> This change is also included in my proposal here
> <https://github.com/richanna/secevent/pull/1>.
>
>
>
> Thanks,
>
> Atul
>
>
> _______________________________________________
> Id-event mailing list
> Id-event@ietf.org
> https://www.ietf.org/mailman/listinfo/id-event
>