There wasn't a newline before a `code-block` in the federation docs, which
didn't allow the formatting of the code block to be rendered properly.
Change-Id: If658db9b6f4458125e5d0c4ad4e727944b0e4fa7
The keystone-all file no longer exists in bin/, but it is automatically
created when Keystone is installed. It was never removed as this bug
originally suggested.
Removing "bin/" from the command 'tools/with_venv.sh bin/keystone-all'
will make with_venv.sh use the keystone-all from the created virtualenv.
Change-Id: I04695f0548d6f87d632b87a40834323fea1378d7
Co-Authored-By: Akshay Aggarwal <akshayx.aggarwal@intel.com>
Co-Authored-By: Jason O'Brien <jasonx.obrien@intel.com>
Closes-Bug: #1462242
Until now all the docs assumed the OS-FEDERATION is still an extension.
Since this is not true since Kilo release, we should also update our
documentation.
We also moved some of the files from the ``extension`` directory to the
``federation`` one.
Change-Id: I7f71fea55accaaaf38b2ee069fab9726c1045b4c
Closes-Bug: #1466092
If the developer doesn't want to use the wip decorator, they
should be able to choose not to. This makes it clear that a
-1 shouldn't be applied if the developer decides not to use
wip.
Change-Id: If041cd1a4e3a1092ab47e6dd81ee03eb772c4c35
A "default" entrypoint is defined for each auth method. The
default driver will be used if there's no config option for the
method, or the config option is not set, or if the config option
is set to "default".
For the external methods, since there's several of them, each gets
a short name that can be used rather than the qualified class.
bp stevedore
DocImpact
Change-Id: I2484af32e9eb3703869cf441e4f9851b54b0db2b
domain_config_upload, fernet_rotate, and fernet_setup are missing
from the online configuration documentation for the keystone-manage
command.
This patch adds them using the descriptions found in the man page.
Change-Id: If916589d2a97614bf252ac12bd013b25acb1aa66
Closes-Bug: #1466957
Implementation of a command line wrapped build on top of mapping engine.
Its main goal is checking effects of input parsed by RuleProcessor with
set of provided mapping rules. User must provide two files: a) rules
file with proper JSON with mapping rules (identical to those uploaded to
the server) b) a file with key-value set of environ-like parameters.
Basic usage:
$ keystone-manage mapping_engine --help
$ keystone-manage mapping_engine --rules <path> --input <path>
Upon successful execution program outputs to the stdout a JSON structure
with effective objects like user, group_ids and user_names.
Implements: bp mapping-engine-tester
Change-Id: Ia4b2e617692ebb42693db6d335985dcb6a0969e1
There's no reason to jump into the interactive interpreter if you only
need to run a single line of code and ensure that it doesn't fail.
Change-Id: I6d593b97517460395ef31a84a986a73a36b82078
Cleans up the sample_data script to replace the keystoneclient commands
with the new openstackclient commands
Change-Id: Id68ff2b466e582a0c2f4418d173f7d63c14f5f37
Closes-Bug: #1459816
By default, the SP is disabled. It should be enabled in order to
retrieve a SAML assertion targeted to it.
Change-Id: I445b59e4e7c68282051aa13e8c4d47485a725d0f
* Remove reference to service provider as being a region
* Change the URL to /ecp
Change-Id: I346d5c8c2558ad7ced8b62a87d133c57b3ec3b8e
Closes-Bug: 1459683
Part of CURL response is not accurate anymore
- There will be no service catalog returned if we get
a token from a existing token.
- Miss `audit_ids` in the response.
Closes-Bug: #1459532
Change-Id: I81db8db37f4ffdad01f976a16c14f45f411db76d
Fix a mismatched <Location> and </LocationMatch> tag in the example
config snippet, and mention that the config should match the identity
provider Location config.
Change-Id: I7dc957d2ccdcc38f2eba305bf857e9449f6a5856
Closes-Bug: #1452197
Replace URLs for workflow documentation to appropriate parts of the
OpenStack Project Infrastructure Manual.
Also update some outdated/obsolete devstack-related URLs.
Change-Id: I84e3a62b0aec7cb62d10b8b41eac27b15326ab5c
The http://ci.openstack.org/ documentation site has been deprecated,
replaced by redirects to corresponding paths within
http://docs.openstack.org/infra/ where other Project Infrastructure
documentation already resides.
Change-Id: Ifbc668063ad7cc8bee6b44279592ea6ca09c35ea
A temporary fix was added to get around a bug in how pbr handles
its autodoc_tree_index_modules setting. Since this bug is fixed we no
longer need the work around.
Change-Id: I6af0fdd6d1efacb47692b89c329e45ac59fef7cb
Closes-Bug: #1260495
The functional tests use Python 3.4 so document that both Python
2.7 and Python 3.4 are required for development and add
python3-dev to the required packages for Ubuntu.
Change-Id: I48cfa5d524338e046b9049280a142702fa961b3d
* Replace the github by openstack's official home git.openstack.org
* Also update the like of developer documentation of keystone
Change-Id: I60e8e914d9fa3be2cdfffe029e4c2432c07962e2
The author of the mod_auth_openidc apache plugin had created a pull
request to update the keystone install instructions for the plugin
https://github.com/openstack/keystone/pull/5
Change-Id: Id6e663a7f20cec3169a43e48ffbf61c881672807
The development doc still references Ubuntu 12.04, even though
our installation guide includes instructions for Ubuntu 14.04.
Change-Id: I92aa5ef7ca224cedb0ef287012fb67f7fe5169e8
Currently, `curl http://0.0.0.0:35357` and `curl http://0.0.0.0:35357/v2.0/`
no longer have the same response, since keystone has it's V3 APIs. Update
the doc to differentiate the two Curl example.
Change-Id: I08f5e3bd502ebd78ea775ea4135b5c3ffb80e9c7
The WebSSO documentation describes the WEBSSO_INITIAL_CHOICE setting,
but it then shows an example with the incorrect configuration setting
name (WEBSSO_CHOICES). This corrects the example.
Change-Id: I2cd261f2377da3738e1b0befe62166dac5c49a2f
The current man pages for keystone-manage don't include commands relating to
Fernet setup, or the domain configuration upload.
Change-Id: Ifd208151470d8d39d3d4851557e45dc12d1a577b
Closes-Bug: #1441300
there are a few extra steps necessary for supporting horizon and
a federated keystone, these need to be documented.
Change-Id: I468e5591de9b77b44de995d855dc9b133bf0e741
When a domain config is modifed, in order for those configs
to actually be live, we need to re-initialise the backend
identity driver for the respective domain.
This patch uses cache timeouts to ensure that new config options
become visible to all keystone processes/threads.
Partially Implements: blueprint domain-config-ext
Change-Id: I1a802dde53f25f945eadd235574e9c342a770443
In developing.rst there is an incorrect reference to the
directory in which the docs are generated.
Closes-Bug: #1438983
Change-Id: I4afa0194f5f7cab3c562806b052be6f4a8d38357
The current configuration documentation describes the existing
file-based domain-specific configuration method. This patch
adds the information on the new SQL-based approach.
DocImpact
Partially Implements: blueprint domain-config-ext
Change-Id: Iff368cf05ab23f4c855ef4f1f286ff1081fd50ca
Add some content in `developing.rst` for how to migrate core
components, primarly includes:
- The dir of core components should also includes version
subdirectory.
- Files: `__init__.py` and `migrate.cfg` also needed for core
components, so we should start a new section.
- Provide example for core components to upgrade or downgrade.
Change-Id: I7080609c043f856fc923a16473b4a49d5f7d06cd