Hi,
I'm trying to build a solution to authorize users to log into devices
based on their group membership in our NMS.
We use ClientListSQL to generate the Client config blocks and I've used
the OSC-Authorize-Group attribute for add the group id's to the request
attributes like:
OSC-Authorize-Gr
Hi,
> On 13 Jul 2017, at 13.59, Hartmaier Alexander
> wrote:
>
> I'm trying to build a solution to authorize users to log into devices
> based on their group membership in our NMS.
>
> We use ClientListSQL to generate the Client config blocks and I've used
> the OSC-Authorize-Group attribute f
Hi,
On 2017-07-13 14:19, Tuure Vartiainen wrote:
Hi,
On 13 Jul 2017, at 13.59, Hartmaier Alexander
wrote:
I'm trying to build a solution to authorize users to log into devices
based on their group membership in our NMS.
We use ClientListSQL to generate the Client config blocks and I've us
Hello,
Just throwing out an idea -
You could do a pre handler hook that combines all incoming OSC-Authorize-Group
values into a single value sorted so you know how they will appear to the
handler.
I'm not a fan of hooks but in this case it might be a working workaround :)
Regards,
Patrik Forsb
Hi,
> On 13 Jul 2017, at 15.56, Hartmaier Alexander
> wrote:
>
> On 2017-07-13 14:19, Tuure Vartiainen wrote:
>>
>>
>> So OSC-Authorize-Group attributes define group ids which are allowed to login
>> to that device?
> It's added metadata for the request which includes all groups the device
>
Hi,
> On 13 Jul 2017, at 15.56, Hartmaier Alexander
> wrote:
>
> On 2017-07-13 14:19, Tuure Vartiainen wrote:
>>
>>
>>> On 13 Jul 2017, at 13.59, Hartmaier Alexander
>>> wrote:
>>>
>>> I'm trying to build a solution to authorize users to log into devices
>>> based on their group membership
