Dell DX6004S DX Object Storage Application Guide - Page 63

Managing Security, for Application Developers

Page 63 highlights

The Castor-Authorization header in this example is: Castor-Authorization: cluster.example.com/_administrators, POST=cluster.example.com 3. PUT the updated realm on the domain: curl -X PUT --data-binary @cluster_example_com -H "Castor-Authorization: cluster.example.com/_administrators, POST=cluster.example.com" -H "Castor-Stream-Type: admin" --anyauth -u "jeannie.clark:jeannie" -location-trusted "http://172.16.0.35?domain=cluster.example.com" -post301 -D domain-realm-put.log 4. GET the user list: curl --anyauth -u "fred.bell:fred" --location-trusted http://172.16.0.35?domain=cluster.example.com -D get-domain-realmput.log The updated user list displays: john.rogers:cluster.example.com:7258c81943bb715d75eb7cfecf4295de jane.lalane:cluster.example.com:98ce0bb175aae28a291a6ecbe545dcd4 Notice that the users you previously added to the realm, such as earl.grey and james.north, are no longer in the realm. This is the result of the PUT operation. 5. HEAD the domain again to verify the Castor-Authorization header has not changed: curl -I --anyauth -u "jeannie.clark:jeannie" --location-trusted http://172.16.0.35?domain=cluster.example.com -D get-domain-realm4.log The Castor-Authorization header is still: Castor-Authorization: cluster.example.com/_administrators, POST=cluster.example.com 6. Provide the list of cluster.example.com realm user names and passwords to your application developers because they will need them to run the examples in Chapter 13, Managing Security for Application Developers. Copyright © 2010 Caringo, Inc. All rights reserved 58 Version 5.0 December 2010

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81

Copyright © 2010 Caringo, Inc.
All rights reserved
58
Version 5.0
December 2010
The
Castor-Authorization
header in this example is:
Castor-Authorization: cluster.example.com/_administrators,
POST=cluster.example.com
3. PUT the updated realm on the domain:
curl -X PUT --data-binary @cluster_example_com -H "Castor-Authorization:
cluster.example.com/_administrators, POST=cluster.example.com" -H
"Castor-Stream-Type: admin" --anyauth -u "jeannie.clark:jeannie" --
post301 -D domain-realm-put.log
4. GET the user list:
curl --anyauth -u "fred.bell:fred" --location-trusted
put.log
The updated user list displays:
john.rogers:cluster.example.com:7258c81943bb715d75eb7cfecf4295de
jane.lalane:cluster.example.com:98ce0bb175aae28a291a6ecbe545dcd4
Notice that the users you previously added to the realm, such as
earl.grey
and
james.north
, are no longer in the realm. This is the result of the PUT operation.
5. HEAD the domain again to verify the
Castor-Authorization
header has not changed:
curl -I --anyauth -u "jeannie.clark:jeannie" --location-trusted
The
Castor-Authorization
header is still:
Castor-Authorization: cluster.example.com/_administrators,
POST=cluster.example.com
6. Provide the list of
cluster.example.com
realm user names and passwords to your application
developers because they will need them to run the examples in
Chapter 13,
Managing Security
for Application Developers
.