Skip to content
This repository has been archived by the owner on Nov 17, 2020. It is now read-only.

When authenticating using a client cert, there is no way to specify a vhost for that client #73

Closed
pickettphil opened this issue Mar 29, 2016 · 2 comments
Closed

When authenticating using a client cert, there is no way to specify a vhost for that client #73

pickettphil opened this issue Mar 29, 2016 · 2 comments
Assignees
@acogoluegnes
Labels
effort-low enhancement
Milestone
3.6.7

Comments

@pickettphil
Copy link

When connecting with username/password, vhost is specified as part of username (vhost:username), but there is no username when authenticating with a client cert. Is there some way to tie a vhost to a user using client cert authentication?

Some possible solutions are:

  1. Use the x509 certificate's optional fields. This could be problematic for many users.
  2. Provide a mapping of user (via client cert) to vhost via runtime parameters.
@michaelklishin michaelklishin added this to the 3.6.x milestone Mar 29, 2016
@michaelklishin michaelklishin removed this from the 3.6.x milestone Dec 1, 2016
@michaelklishin
Copy link
Member

We are investigating this for 3.6.7.

acogoluegnes added a commit to rabbitmq/rabbitmq-server that referenced this issue Dec 12, 2016
@acogoluegnes
Improve global runtime parameters support
9966bf2 
References rabbitmq/rabbitmq-mqtt#73
acogoluegnes added a commit that referenced this issue Dec 13, 2016
@acogoluegnes
Introduce mqtt_default_vhosts global parameter
56ecb5d 
Fixes #73
@acogoluegnes acogoluegnes mentioned this issue Dec 13, 2016
Merged
acogoluegnes added a commit to rabbitmq/rabbitmq-server that referenced this issue Dec 13, 2016
@acogoluegnes
Use atom key and JSON value for global parameters
1a8e5c9 
Part of rabbitmq/rabbitmq-mqtt#73
@acogoluegnes acogoluegnes mentioned this issue Dec 13, 2016
Merged
acogoluegnes added a commit that referenced this issue Dec 13, 2016
@acogoluegnes
Add test case for cert user/vhost mapping
455c0e7 
Fixes #73
@acogoluegnes acogoluegnes mentioned this issue Dec 14, 2016
Merged
acogoluegnes added a commit to rabbitmq/rabbitmq-server that referenced this issue Dec 14, 2016
@acogoluegnes
Document global parameters CLI commands
f18311a 
Part of rabbitmq/rabbitmq-mqtt#73
acogoluegnes added a commit to rabbitmq/rabbitmq-website that referenced this issue Dec 14, 2016
@acogoluegnes
Document MQTT cert/vhost mapping
92bfb96 
Part of rabbitmq/rabbitmq-mqtt#73
@acogoluegnes acogoluegnes mentioned this issue Dec 14, 2016
Merged
acogoluegnes added a commit to rabbitmq/rabbitmq-server that referenced this issue Dec 14, 2016
@acogoluegnes
List all global parameters
ee9a020 
Including the cluster_name.

References rabbitmq/rabbitmq-mqtt#73
acogoluegnes added a commit to rabbitmq/rabbitmq-management that referenced this issue Dec 14, 2016
@acogoluegnes
Fix global parameters test
344777f 
References rabbitmq/rabbitmq-mqtt#73
@michaelklishin michaelklishin mentioned this issue Dec 15, 2016
Closed
@michaelklishin michaelklishin added this to the 3.6.7 milestone Dec 15, 2016
@michaelklishin
Copy link
Member

Merged into stable, needs merging into master (and porting CLI changes to the new CLI repo).

michaelklishin pushed a commit to rabbitmq/rabbitmq-website that referenced this issue Dec 15, 2016
@acogoluegnes @michaelklishin
Document MQTT cert/vhost mapping
7564e4d 
Part of rabbitmq/rabbitmq-mqtt#73
acogoluegnes added a commit to rabbitmq/rabbitmq-cli that referenced this issue Dec 16, 2016
@acogoluegnes
Add global parameters commands
8a61e8c 
Part of rabbitmq/rabbitmq-mqtt#73
@acogoluegnes acogoluegnes mentioned this issue Dec 16, 2016
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@acogoluegnes acogoluegnes

Labels
effort-low enhancement
Projects
None yet
Milestone
3.6.7
Development

No branches or pull requests
3 participants
@michaelklishin @acogoluegnes @pickettphil