Hi,
I want to replace an existing WebSEAL, which uses eai for authentication, with an IAG. But it seems IAG, when using eai, supports only levels 0 and 1. At least I didn't find a configuration entry to add additional levels.

When using OIDC as authentification, the supplied level is accepted without problem

My questions:

1) is there a config entry in the yaml config to add additional levels?

2) if not, what is the best practice to edit the webseal.conf file to add the levels? Is it even possible to adapt the WebSEAL config file or is it recommended to not touch it?

Kind regards,

Hi,
I want to replace an existing WebSEAL, which uses eai for authentication, with an IAG. But it seems IAG, when using eai, supports only levels 0 and 1. At least I didn't find a configuration entry to add additional levels.

When using OIDC as authentification, the supplied level is accepted without problem

My questions:

1) is there a config entry in the yaml config to add additional levels?

2) if not, what is the best practice to edit the webseal.conf file to add the levels? Is it even possible to adapt the WebSEAL config file or is it recommended to not touch it?

Kind regards,

Hi Scott,

Thanks for your answer.

I already know how the new model of IAG works and I like it a lot. It is much more flexible than the legacy one on WebSEAL.

But here I want to migrate an existing eai without touching the part that does the eai as it is used on many WebSEALs and I want to migrate them one by one. That's why it is not an option to just set that AUTHENTICATION_LEVEL always to 1 as that would break the old WebSEALS. The eai will answer with a level 5, which will throw an error on IAG.

So I understand there isn't an option in the yaml file to set configure new levels.

What about changing the WebSEAL conf file? Is this possible or recommended? It is a trivial change to make, but I'm not sure it will be persistent and not just be overwritten by IAG.

Kind regards,

Hi,
I want to replace an existing WebSEAL, which uses eai for authentication, with an IAG. But it seems IAG, when using eai, supports only levels 0 and 1. At least I didn't find a configuration entry to add additional levels.

When using OIDC as authentification, the supplied level is accepted without problem

My questions:

1) is there a config entry in the yaml config to add additional levels?

2) if not, what is the best practice to edit the webseal.conf file to add the levels? Is it even possible to adapt the WebSEAL config file or is it recommended to not touch it?

Kind regards,

Hi Scott,

Thanks for your answer.

I already know how the new model of IAG works and I like it a lot. It is much more flexible than the legacy one on WebSEAL.

But here I want to migrate an existing eai without touching the part that does the eai as it is used on many WebSEALs and I want to migrate them one by one. That's why it is not an option to just set that AUTHENTICATION_LEVEL always to 1 as that would break the old WebSEALS. The eai will answer with a level 5, which will throw an error on IAG.

So I understand there isn't an option in the yaml file to set configure new levels.

What about changing the WebSEAL conf file? Is this possible or recommended? It is a trivial change to make, but I'm not sure it will be persistent and not just be overwritten by IAG.

Kind regards,

Hi,
I want to replace an existing WebSEAL, which uses eai for authentication, with an IAG. But it seems IAG, when using eai, supports only levels 0 and 1. At least I didn't find a configuration entry to add additional levels.

When using OIDC as authentification, the supplied level is accepted without problem

My questions:

1) is there a config entry in the yaml config to add additional levels?

2) if not, what is the best practice to edit the webseal.conf file to add the levels? Is it even possible to adapt the WebSEAL config file or is it recommended to not touch it?

Kind regards,

Hi Scott,

Thanks for your answer.

I already know how the new model of IAG works and I like it a lot. It is much more flexible than the legacy one on WebSEAL.

But here I want to migrate an existing eai without touching the part that does the eai as it is used on many WebSEALs and I want to migrate them one by one. That's why it is not an option to just set that AUTHENTICATION_LEVEL always to 1 as that would break the old WebSEALS. The eai will answer with a level 5, which will throw an error on IAG.

So I understand there isn't an option in the yaml file to set configure new levels.

What about changing the WebSEAL conf file? Is this possible or recommended? It is a trivial change to make, but I'm not sure it will be persistent and not just be overwritten by IAG.

Kind regards,

Hi,
I want to replace an existing WebSEAL, which uses eai for authentication, with an IAG. But it seems IAG, when using eai, supports only levels 0 and 1. At least I didn't find a configuration entry to add additional levels.

When using OIDC as authentification, the supplied level is accepted without problem

My questions:

1) is there a config entry in the yaml config to add additional levels?

2) if not, what is the best practice to edit the webseal.conf file to add the levels? Is it even possible to adapt the WebSEAL config file or is it recommended to not touch it?

Kind regards,