yahoo-eng-team team mailing list archive

[Dolph Mathews <1218405@xxxxxxxxxxxxxxxxxx>]

This is by design. The goal is to require users to opt-in to optional
extensions rather than to recommend them *all* in our sample
configuration. Pipeline extensions should be documented as much as
possible through sample configuration, but remain disabled. If we have a
scenario where "every deployment should have this enabled" then we can
discuss putting it in the sample pipeline (or, more likely... adding it
to the core API).

** Changed in: keystone
       Status: In Progress => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to Keystone.
https://bugs.launchpad.net/bugs/1218405

Title:
  enable oauth extension in v3.0 app pipeline

Status in OpenStack Identity (Keystone):
  Invalid

Bug description:
  I see oauth is put in some configuration of keystone.conf.sample:
  [auth]
  methods = external,password,token,oauth1

  so I think we had better enable it in keystone-paste.ini:
  [filter:oauth_extension]
  paste.filter_factory = keystone.contrib.oauth1.routers:OAuth1Extension.factory

  [pipeline:api_v3]
  pipeline = access_log sizelimit url_normalize token_auth admin_token_auth xml_body json_body ec2_extension s3_extension service_v3   --> add oauth_extension

To manage notifications about this bug go to:
https://bugs.launchpad.net/keystone/+bug/1218405/+subscriptions