[ogpx] Authenticating rez_avatar/request?

"Hurliman, John" <john.hurliman@intel.com> Wed, 27 January 2010 01:57 UTC

Return-Path: <john.hurliman@intel.com>
X-Original-To: ogpx@core3.amsl.com
Delivered-To: ogpx@core3.amsl.com
Received: from localhost (localhost [127.0.0.1]) by core3.amsl.com (Postfix) with ESMTP id 5271E3A6993 for <ogpx@core3.amsl.com>; Tue, 26 Jan 2010 17:57:25 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -6.226
X-Spam-Level:
X-Spam-Status: No, score=-6.226 tagged_above=-999 required=5 tests=[AWL=0.372, BAYES_00=-2.599, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_MED=-4]
Received: from mail.ietf.org ([64.170.98.32]) by localhost (core3.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id EtNVnL5JS0j0 for <ogpx@core3.amsl.com>; Tue, 26 Jan 2010 17:57:24 -0800 (PST)
Received: from mga02.intel.com (mga02.intel.com [134.134.136.20]) by core3.amsl.com (Postfix) with ESMTP id 9AA8A3A6988 for <ogpx@ietf.org>; Tue, 26 Jan 2010 17:57:24 -0800 (PST)
Received: from orsmga002.jf.intel.com ([10.7.209.21]) by orsmga101.jf.intel.com with ESMTP; 26 Jan 2010 17:56:35 -0800
X-ExtLoop1: 1
X-IronPort-AV: E=Sophos; i="4.49,349,1262592000"; d="scan'208,217"; a="487314814"
Received: from rrsmsx603.amr.corp.intel.com ([10.31.0.57]) by orsmga002.jf.intel.com with ESMTP; 26 Jan 2010 17:57:24 -0800
Received: from rrsmsx601.amr.corp.intel.com (10.31.0.151) by rrsmsx603.amr.corp.intel.com (10.31.0.57) with Microsoft SMTP Server (TLS) id 8.2.176.0; Tue, 26 Jan 2010 18:57:34 -0700
Received: from rrsmsx506.amr.corp.intel.com ([10.31.0.39]) by rrsmsx601.amr.corp.intel.com ([10.31.0.151]) with mapi; Tue, 26 Jan 2010 18:57:33 -0700
From: "Hurliman, John" <john.hurliman@intel.com>
To: "ogpx@ietf.org" <ogpx@ietf.org>
Date: Tue, 26 Jan 2010 18:57:31 -0700
Thread-Topic: Authenticating rez_avatar/request?
Thread-Index: Acqe9BXsF5qKC3nWQbaMCEmCg0dc0w==
Message-ID: <62BFE5680C037E4DA0B0A08946C0933DC7216665@rrsmsx506.amr.corp.intel.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
x-cr-puzzleid: {E2D4D88A-84A1-4DD7-AE9E-15703F2C5D4A}
x-cr-hashedpuzzle: AK6W AK72 BgVF Bng0 CLdH CrdL DxEW EGzU EP4W ErZ7 FNkf FnfZ Ftgn GIrx GRDB HCCi; 1; bwBnAHAAeABAAGkAZQB0AGYALgBvAHIAZwA=; Sosha1_v1; 7; {E2D4D88A-84A1-4DD7-AE9E-15703F2C5D4A}; agBvAGgAbgAuAGgAdQByAGwAaQBtAGEAbgBAAGkAbgB0AGUAbAAuAGMAbwBtAA==; Wed, 27 Jan 2010 01:57:31 GMT; QQB1AHQAaABlAG4AdABpAGMAYQB0AGkAbgBnACAAcgBlAHoAXwBhAHYAYQB0AGEAcgAvAHIAZQBxAHUAZQBzAHQAPwA=
acceptlanguage: en-US
Content-Type: multipart/alternative; boundary="_000_62BFE5680C037E4DA0B0A08946C0933DC7216665rrsmsx506amrcor_"
MIME-Version: 1.0
Subject: [ogpx] Authenticating rez_avatar/request?
X-BeenThere: ogpx@ietf.org
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: Virtual Worlds and the Open Grid Protocol <ogpx.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/ogpx>
List-Post: <mailto:ogpx@ietf.org>
List-Help: <mailto:ogpx-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/ogpx>, <mailto:ogpx-request@ietf.org?subject=subscribe>
X-List-Received-Date: Wed, 27 Jan 2010 01:57:25 -0000

On the region domain side, how is a region able to identify which AD is calling rez_avatar/request? The LL Vaak regions seem to have some way of knowing if the call is being made by a trusted AD because a message is returned about an unauthorized user if I try to login with my own AD. What is the proper way of implementing the same whitelisting functionality in my own region domain code?

John