restrict 3rd party app to church memberhship (SSO)?

Similar sentiments with with other API and integration topics but rather than wanting to access data I would like to restrict data to members - preferably unit membership but world wide membership would be fine too. Is there a process to apply for SSO such that an third-party app can be many only available for LDS account holders?

I would just like to have Unit site that did not require members to use social media where their membership info is indirectly leaked and I am prompting all the social ills that come with adtech (misinfo, porn, other digital addictions). There does not seem to be a path for this, regardless of calling. In comparison, If I were making a site for a BYU student group, we could restrict the site to authenticated users and users can authenticate via their Church Account. Im not sure of the current implementation but I bet I could look at the identity provider and restrict the site to users whom have authenticated with a Church Account (did something simulate for AWS access when I worked at BYU).

Assuming no such process exists, how come student groups are allowed to do this but unit leaders are not?

Access to APIs outside official Church development efforts is not allowed. Any websites, programs, and apps that use Church Account credentials are under the control and development of the Church ICS department and certain affiliates.

So the only solution is to export unit member data into an external system for parallel user accounts.

tomdavidson wrote: Wed Dec 27, 2023 5:14 pm So the only solution is to export unit member data into an external system for parallel user accounts.

When discovered, that would likely warrant a call from church security department. The systems used to allow exporting of data, but it was removed.