Databases
StackOverflow2013
Postsdbo
POUser management in passive federation
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POUser management in passive federation
    primarykey
    data
    text
    <p>I have with usage of Windows Identity Framework (WIF) created IP-STS and three separate Relying Parties under the one federation. Federated Single Sing On and Sign Out scenarios work fine. This is prepared as an demo.</p> <p>What is my problem ?</p> <p>In production I have to unify 3 different web applications under the on identity roof. Currently all of these applications have different authentication and authorization mechanisms, in data store different set of tables are assigned for specific users etc. For sign on and sign out everything is clear to me. Problem is with creation of new users. Is there any general pattern in these scenarios. Why I am asking this. When you go deeper in this case you can find that is not so simple. For first web app we have a set of fields that have been supported (most of these are some enumerations from DB), from second set of others... So, I need to have all of the data for this process from all Relying parties. How to accomplish this ? One approach is to use set of IFRAMES or something like that ? Also I will need to have new user in each application because of relations tables in separate applications that relies on user entity. It looks to me very complex and I am curios is there any well known pattern for this cases. I am sure that I am not a first who have to unified totally different applications under one identity management.</p> <p><strong>UPDATED</strong> : I have found that this is part of the provisioning management or federated provisioning. Also I have found that it could be realized by SPML protocol that is going hand by hand with SAML protocol. Is there any protocol or point of integration in WIF for these purposes ?</p> <p>Regards, Rastko</p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USRastko
    1. USRastko
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload