Vendor-Specific attribute with rlm_rest

[Bjørn Mork]

"Michael A Carpenter - macarpen at us.ibm.com" <macarpen at us.ibm.com>
writes:

> I'm trying to return the Vendor-Specific attribute with value "H=4,I=4" using the rlm_rest module. I've tried the following authorization response payloads:
>
> {"Attr-26": "0x483d342c493d34"}
>
> {"Vendor-Specific": "H=4,I=4"}
>
> Both resulted in error:
>
> (0) aaa-api: Processing response header
> (0) aaa-api:   Status : 200 (OK)
> (0) aaa-api:   Type   : json (application/json)
> (0) aaa-api: Parsing attribute "Attr-26"
> (0) aaa-api: EXPAND 0x483d342c493d34
> (0) aaa-api:    --> 0x483d342c493d34
> (0) aaa-api: WARNING: Incompatible value assignment for attribute "Vendor-Specific", skipping...
>
> (1) aaa-api: Processing response header
> (1) aaa-api:   Status : 200 (OK)
> (1) aaa-api:   Type   : json (application/json)
> (1) aaa-api: Parsing attribute "Vendor-Specific"
> (1) aaa-api: EXPAND H=4,I=4
> (1) aaa-api:    --> H=4,I=4
> (1) aaa-api: WARNING: Incompatible value assignment for attribute "Vendor-Specific", skipping...
>
> Any suggestions for what might be incompatible about the value?

It must be prefixed with a type, length and enterprise number.  See
https://tools.ietf.org/html/rfc2865#section-5.26



Bjørn