User Tools
public:chargeable_user_identity
Differences
This shows you the differences between two versions of the page.
|
public:chargeable_user_identity [2022/05/27 12:32] admin created |
public:chargeable_user_identity [2022/05/27 12:39] (current) admin [How do I generate a CUI for a user (Home site)?] |
||
|---|---|---|---|
| Line 17: | Line 17: | ||
| If you receive a CUI request RFC 4372 says you should respond with the CUI for the user being authenticated. Whilst the RFC doesn’t specify the method, a CUI must be a transformation of the username. Therefore the recommended method for govroam is to MD5 hash the username together with a salt(*) and the visited site Operator Name. | If you receive a CUI request RFC 4372 says you should respond with the CUI for the user being authenticated. Whilst the RFC doesn’t specify the method, a CUI must be a transformation of the username. Therefore the recommended method for govroam is to MD5 hash the username together with a salt(*) and the visited site Operator Name. | ||
| - | Ideally the Visited site ORPS should send their Operator Name (Attribute 126) together with the CUI Request, however in cases where this is absent, the govroam NRPSs will inject Operator-Name on behalf of the Visited site using the value in the Identifier field in the Organisation setting panel on the Configure page on Support server. | ||
| =====What does govroam say about CUI?===== | =====What does govroam say about CUI?===== | ||
public/chargeable_user_identity.txt · Last modified: 2022/05/27 12:39 by admin
Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Share Alike 4.0 International
