Bug 497549 - Multiple issues in Authentication chapter of Installation Guide
Summary: Multiple issues in Authentication chapter of Installation Guide
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise MRG
Classification: Red Hat
Component: Messaging_Installation_and_Configuration_Guide
Version: Development
Hardware: All
OS: Linux
low
medium
Target Milestone: 1.2
: ---
Assignee: Lana Brindley
QA Contact: MRG Quality Engineering
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-24 16:07 UTC by Jonathan Robie
Modified: 2013-10-23 23:13 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-10-12 00:55:44 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jonathan Robie 2009-04-24 16:07:42 UTC
This chapter should describe what is installed by default, and how users can use an authorization-enabled server, doing this at a high level before descending into details. 

I think the intro should say:

- Both the server and the clients are integrated with SASL
- SASL uses the account a program is running in to identify the user and supply authentication
- As we install it, you have to run the server either as root or as the qpidd user - if you run as a daemon, this happens automatically, but if you run from the command line authentication can be trickier
- A 'guest' account is created by the installation program
- You can set up other accounts or see what accounts exist (see later discussion of saslpasswd2 and sasldblistusers2)


Some details for the further discussion:

- default authentication depends on the cyrus configuration on the box, it is not usually PLAIN
- need to discuss using the guest account in clients vs. connecting using the user account
- need to discuss ANONYMOUS authentication

Comment 1 Lana Brindley 2009-10-12 00:53:55 UTC
This section got thoroughly overhauled for the last release. Which version are you looking at?

Also, I think it's important we don't go into a massive amount of detail. The idea is to give an overview of the authentication capabilities, and then point the reader to the user guide for the complete run down.

LKB


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