Hi All,

Since we are moving to file base deployment for sp/idp, we have to create
these files using yaml. While doing that we thought to resolve some issues
and generalize the sp/idp files.
As we have now in IS 5.3.0, we configure local authenticator in SP and
federated authenticator in IDP file. But it doesn't make sense to specially
treat to the local authenticator in SP side and we can consider it also as
another idp. We can name it as resident-idp and SP authenticator can point
the idp name when it want to use local one as same as it use federated one.
We can keep other resident identity provider configuration like password
policies, login policies, etc.. in separate config file that is decouple
with the outbound authentication flow. This will not effect for the
existing framework implementation but only change the user experience that
is more cleaner than now. I have attached the sample sp file, sample idp
file and resident idp file with this, it would be great if i can get more
feedbacks about this.

thanks

*Harsha Thirimanna*
*Associate Tech Lead | WSO2*

Email: hars...@wso2.com
Mob: +94715186770
Blog: http://harshathirimanna.blogspot.com/
Twitter: http://twitter.com/harshathirimann
Linked-In: linked-in:
http://www.linkedin.com/pub/harsha-thirimanna/10/ab8/122
<http://wso2.com/signature>

Attachment: resident-idp.yaml
Description: application/yaml

Attachment: sample.yaml
Description: application/yaml

Attachment: myidp.yaml
Description: application/yaml

_______________________________________________
Architecture mailing list
Architecture@wso2.org
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture

Reply via email to