IETF Logo Mail Archive

[OAUTH-WG] Authorization Server

Richard Snowden <richard.t.snowden@gmail.com> Thu, 17 July 2014 08:47 UTC

Return-Path: <richard.t.snowden@gmail.com>
X-Original-To: oauth@ietfa.amsl.com
Delivered-To: oauth@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 0E8CB1A0109 for <oauth@ietfa.amsl.com>; Thu, 17 Jul 2014 01:47:14 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] 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 ji9q5RLURhCe for <oauth@ietfa.amsl.com>; Thu, 17 Jul 2014 01:47:12 -0700 (PDT)
Received: from mail-ig0-x22a.google.com (mail-ig0-x22a.google.com [IPv6:2607:f8b0:4001:c05::22a]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 94EA61A00F3 for <oauth@ietf.org>; Thu, 17 Jul 2014 01:47:12 -0700 (PDT)
Received: by mail-ig0-f170.google.com with SMTP id h3so5407740igd.1 for <oauth@ietf.org>; Thu, 17 Jul 2014 01:47:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=Y55Q/YWvAS2muHRNMXDmp14R3ko47wsvsd4HSOkcrJs=; b=LDcrXXvbrqO+1H9cKw8sq20CaxxRIpB5ucuTFcRjHq0TkKfQ2wcd5oFNmR/50P85hm GIGGYQzOyWqnbZIKznHvwJkG1Egg8y8hHIWNTEfQmsf5y2SCScByJL2Oq94ZWSZWp0Jo dHPeyA1b/3jP7apaQKejbqKG5s/MuXpsOYJvOtid5bCK5xAOA4dl2YShRZDKU4snTfX/ V9sQ4TmISyImrY2h7UuLnCCULDN7DjU6R/lYeBgzOf5fIV7vyZdhSIYuX6cenH0EWTF/ h8DGs9eP9MdHBQYZf9GuzbsAFwsQD/muGDKAUncYgXOputAGaFHT8Jbcyx3B3V15FISV UgkA==
MIME-Version: 1.0
X-Received: by 10.60.155.231 with SMTP id vz7mr43699392oeb.56.1405586831784; Thu, 17 Jul 2014 01:47:11 -0700 (PDT)
Received: by 10.60.56.162 with HTTP; Thu, 17 Jul 2014 01:47:11 -0700 (PDT)
Date: Thu, 17 Jul 2014 10:47:11 +0200
Message-ID: <CAH59oZfZbKopao1aFs+kTaEg_5fQXVWBFnRPaFLWmk1Fd6BG7Q@mail.gmail.com>
From: Richard Snowden <richard.t.snowden@gmail.com>
To: oauth@ietf.org
Content-Type: multipart/alternative; boundary="047d7bd7668ecf425b04fe5faffe"
Archived-At: http://mailarchive.ietf.org/arch/msg/oauth/HWBGES_OuidOCJc73dLS6hJ2GYQ
Subject: [OAUTH-WG] Authorization Server
X-BeenThere: oauth@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: OAUTH WG <oauth.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/oauth>, <mailto:oauth-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/oauth/>
List-Post: <mailto:oauth@ietf.org>
List-Help: <mailto:oauth-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/oauth>, <mailto:oauth-request@ietf.org?subject=subscribe>
X-List-Received-Date: Thu, 17 Jul 2014 08:52:55 -0000

Hi there,

after viewing some tutorials and running some samples code I understood the
client side of OAuth 2.0.

Using existing Authorization Server seems to be not too complicated.

Question is: How to implement my own Authorization Server?

Since many companies have their own User/Privilege system, LDAP based (e.g.
Active Directory), etc. - they must have their own Authorization Server.

Is there a framework, libraries, etc. for that? Or do I have to write the
code from scratch?

cheers,
Richard

v2.23.0 | Report a Bug | By Email