[scim] scim over messaging
Chris Hyzer <mchyzer@isc.upenn.edu> Tue, 13 October 2015 20:00 UTC
Return-Path: <mchyzer@isc.upenn.edu>
X-Original-To: scim@ietfa.amsl.com
Delivered-To: scim@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id E46481A8A0E for <scim@ietfa.amsl.com>; Tue, 13 Oct 2015 13:00:32 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.645
X-Spam-Level:
X-Spam-Status: No, score=-1.645 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-2.3, SPF_SOFTFAIL=0.665, T_RP_MATCHES_RCVD=-0.01] autolearn=ham
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 TFTxiYsHGlIq for <scim@ietfa.amsl.com>; Tue, 13 Oct 2015 13:00:31 -0700 (PDT)
Received: from exch-chub03.exchange.upenn.edu (exch-chub03.exchange.upenn.edu [128.91.3.44]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 726EA1A8A0D for <scim@ietf.org>; Tue, 13 Oct 2015 13:00:31 -0700 (PDT)
Received: from exch-mbx01.exchange.upenn.edu ([fe80::10fd:fb9c:1d0c:81a6]) by exch-chub03.exchange.upenn.edu ([fe80::65a2:dd84:9750:16a6%11]) with mapi id 14.03.0235.001; Tue, 13 Oct 2015 16:00:28 -0400
From: Chris Hyzer <mchyzer@isc.upenn.edu>
To: "scim@ietf.org" <scim@ietf.org>
Thread-Topic: scim over messaging
Thread-Index: AdEF8c3fBlbEgTnzTZCHJHgvVQL+yg==
Date: Tue, 13 Oct 2015 20:00:27 +0000
Message-ID: <04BE669BEE19E54BBDC2A9A2585BB688A7A3B3D4@exch-mbx01.exchange.upenn.edu>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-originating-ip: [130.91.219.176]
Content-Type: multipart/alternative; boundary="_000_04BE669BEE19E54BBDC2A9A2585BB688A7A3B3D4exchmbx01exchan_"
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/scim/l5TLz4EsletjAVFM7fsEBLO2E98>
Subject: [scim] scim over messaging
X-BeenThere: scim@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: Simple Cloud Identity Management BOF <scim.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/scim>, <mailto:scim-request@ietf.org?subject=unsubscribe>
List-Archive: <https://mailarchive.ietf.org/arch/browse/scim/>
List-Post: <mailto:scim@ietf.org>
List-Help: <mailto:scim-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/scim>, <mailto:scim-request@ietf.org?subject=subscribe>
X-List-Received-Date: Tue, 13 Oct 2015 20:00:33 -0000
Has there been discussion about SCIM over messaging?
Ie. If sending SCIM through a messaging system (e.g. AWS SQS, activeMQ, etc) where it is not HTTP. Basically this means there is no response, and the request would need whatever would normally be in HTTP be in the message object. E.g.
{
"method": "PATCH",
"resource": "/Groups/acbf3ae7-8463-4692-b4fd-9b4da3f908ce"
"body": {
"schemas": ["urn:scim:schemas:core:1.0"],
"members": [
{
"display": "Babs Jensen",
"value": "pennperson:12345678",
"operation": "delete"
}
]
}
}
Is something like this something that could be added to a future roadmap if not there already?
Thanks,
Chris
Ps. tried to send this earlier, sorry if this is a dupe
- [scim] scim over messaging Chris Hyzer
- Re: [scim] scim over messaging Phil Hunt
- Re: [scim] scim over messaging Chris Hyzer