Authentication Provider Usage about biemond-orawls HOT 5 CLOSED

Hi Brad,

a tricky use case. The problem is that authentication providers have dynamic attributes so they can't be properties and have to be params. So we can add some option to the domain creation or maybe much better have its own type/provider.

I think there is only one DefaultIdentityAsserter and its important/required to weblogic plus has fixed attributes so moving to its own type provider is the best option.

The re-ordering of the providers is also interesting and difficult. What I almost do, is just changing one provider to be the first, else you probably have to add all providers to the puppet configuration. Or do you have multiple providers where you have the change the order/
So maybe an property or param attribute called order with first or last as value

Cheers

from biemond-orawls.

Hi Brad,

I have a similar issue. I have heard from Edwin, that you already send a pull request for the ordering of the providers? Can you send me your changes so I can have a look for my code?

Regards,

Marc

from biemond-orawls.

Hi Marc,

I have an update that will allow you to order the auth providers based on hiera config value. I will push these to my fork sometime in the next few hours and then create a pull request. I'll also update this thread once my fork is updated so you can pull the changes immediately if you want.

from biemond-orawls.

Hi Marc, Edwin,

The ordering change is in my latest pull request. This should solve the the ordering problem as discussed in this issue. I think in most cases it will be fine for users to simply set their custom provider with order: '0'

Still need to work out a solution for refreshing the DefaultIdentityAsserter on domain creation/change.

Cheers,
Brad

from biemond-orawls.

Thanks Brad for the update.

I am also working on a solution of sorting the providers. I am testing it
right now.

Edwin may choose which solution fits best. :-)

Marc

2014-10-10 5:53 GMT+02:00 Brad McNaughton [email protected]:

Hi Marc, Edwin,

The ordering change is in my latest pull request. This should solve the
the ordering problem as discussed in this issue. I think in most cases it
will be fine for users to simply set their custom provider with order: '0'

Still need to work out a solution for refreshing the
DefaultIdentityAsserter on domain creation/change.

Cheers,
Brad

—
Reply to this email directly or view it on GitHub
#57 (comment)
.

from biemond-orawls.