Re: [Architecture] Alternative to using sso-idp-config.xml

Yes, from IS 4.1.0 onward we have removed the 'org.wso2.stratos.identity.saml2.sso.mgt' bundle and the sso-idp-config.xml due to the reason it is only used by the Stratos Manager. We can re-add it in the next IS release without any problem. However, I'm not clear why reading of this file is done b

Re: [Architecture] Alternative to using sso-idp-config.xml

Hi folks, As discussed its pretty clear that we need to support the sso-idp-config.xml in to register SPs. However the released IS 4.5.0 doesn't support this, even if we create the file in repository/conf/ directory there is no bundle to parse the config and register the SP. Previously we has the

Re: [Architecture] Issue at tenant user login in cluster mode - Mutiple user stores active

Thanks, Pushpalanka Jayawardhana Software Engineer WSO2 Lanka (pvt) Ltd [image: Facebook] [image: Twitter] [image: LinkedIn]

Re: [Architecture] Issue at tenant user login in cluster mode - Mutiple user stores active

> > > Won't it be late to load the tenant at this moment? As the changes needs > to be checked out from the repo , for authentication to be successful, are > we to hold the decision using some mechanism till the check out completes? > This is the same behavior you see when you login to management

Re: [Architecture] Issue at tenant user login in cluster mode - Mutiple user stores active

Hi All, I think it's quite acceptable if the users of the newly added userstore are not being able to login within a timeframe (like 5 min in production) . So what if we send the LoadTenant Cluster messages to the worker nodes after a new userstore is being added, after the worker nodes have loade

Re: [Architecture] Issue at tenant user login in cluster mode - Mutiple user stores active

Thanks, Pushpalanka Jayawardhana Software Engineer WSO2 Lanka (pvt) Ltd [image: Facebook] [image: Twitter] [image: LinkedIn]

Re: [Architecture] Issue at tenant user login in cluster mode - Mutiple user stores active

On Thu, Sep 26, 2013 at 5:26 PM, Prabath Siriwardena wrote: > +1 for that.. Only downside - tenant is loaded not on demand.. > That message has to be used with care. Should only send that message during adding user stores. It should not be sent for other cases for which the tenant not being loade

Re: [Architecture] Issue at tenant user login in cluster mode - Mutiple user stores active

+1 for that.. Only downside - tenant is loaded not on demand.. Another approach is.. Currently the tenant is loaded by looking at the URL.. say for example - if the url says - /t/wso2.com - this will make wso2.com to be loaded if it is not loaded already. The issue with authentication is - we do

Re: [Architecture] Issue at tenant user login in cluster mode - Mutiple user stores active

Hmm... very interesting problem :) What we could do is this... We can implement a LoadTenant Cluster message. When that is received, all nodes would load the tenants. We can get depsync to follow. That way, every node will properly load the new user stores. IS can send this message. Azeez On T

[Architecture] Issue at tenant user login in cluster mode - Mutiple user stores active

Hi, This with regard to the issue [1], which is a known issue in IS 4.5.0. Issue reproduced with following steps. Set up cluster with two IS nodes (Depsync enabled). Create a tenant(wso2.com) Wait till the tenant is unloaded in the worker node Add a secondary user store in master node Add a user(