Bug 2209271 - [GSS][DOC] rgw_sts_key explanation is missing in the RGW developer guide
Summary: [GSS][DOC] rgw_sts_key explanation is missing in the RGW developer guide
Keywords:
Status: RELEASE_PENDING
Alias: None
Product: Red Hat Ceph Storage
Classification: Red Hat Storage
Component: Documentation
Version: 6.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: 6.1z1
Assignee: Ranjini M N
QA Contact: Hemanth Sai
Anjana Suparna Sriram
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-05-23 09:56 UTC by Karun Josy
Modified: 2023-07-21 06:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHCEPH-6714 0 None None None 2023-05-23 09:58:10 UTC

Description Karun Josy 2023-05-23 09:56:42 UTC
Describe the issue:

In the section "3.2.8.2. Configuring the Secure Token Service" we explain the usage of "rgw_sts_key" and has given an example

ceph config set RGW_CLIENT_NAME rgw_sts_key STS_KEY
ceph config set client.rgw rgw_sts_key 9a2142613c504c42a23ba2b82147dc28

But in upstream we explicitly ask the key to be 16 hex characters
===========
rgw_sts_key = {sts key for encrypting/ decrypting the session token, exactly 16 hex characters}
===========

https://docs.ceph.com/en/latest/radosgw/STSLite/


This information is missing from the document :

https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/6/html/developer_guide/ceph-object-gateway-and-the-s3-api#secure-token-service_dev


Chapter/Section Number and Title:

3.2.8.2. Configuring the Secure Token Service


Product Version:
RHCS 6

Any other versions of this document that also needs this update:

Yes, RHCS 5 
https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/5/html/developer_guide/ceph-object-gateway-and-the-s3-api#configuring-the-secure-token-service_dev


Note You need to log in before you can comment on or make changes to this bug.