 Fred_PinelMember
Fred_PinelMember            
            
                             
                     Fred_PinelMember
Fred_PinelMember            
            
                             
                    Please sign in to your OneAll account to ask a new question or to contribute to the discussions.
Please click on the link below to connect to the forum with your OneAll account.
Answers
I think the best way to store this in vanilla would be a (seperate) table in the database with the information you supplied. I already noticed that you generate a record in the gdn_oasl_identity table where you link the identity (PK) with the user (FK). Perhaps it would be an idea to add a column called: provider_primary_identity where it stores the primary identifier for that particular provider, if any. In most cases this information will be publicly accessable. When it isn't you could always fill this field with null.
This way I can access the primary identifier for each service in my own database without making thousands, or in some other cases ten-thousands, of API calls per day.