Skip to content
Merulan

LinkedIn setup

What an operator supplies to connect the LinkedIn Source, and the verification the provider requires.

Connecting LinkedIn is opened by Merulan support on the operator behalf. Merulan support holds the credential. An operator who holds the material below connects in one pass.

Prerequisites

LinkedIn refuses the connection until every item holds.

  • A LinkedIn account the aggregator may sign in to.
  • A Merulan support request, because the LinkedIn connection is opened out of band rather than from the Console.

Credentials

LinkedIn stores the credential under the operated custody the registry declares, so Merulan never shows the secret again once the connection is saved.

  • No secret is typed into Merulan. Merulan support opens a hosted sign-in session with the vendor, and the resolved handle lands on the connection row.

Scopes

LinkedIn carries no scope list in Merulan: the aggregator account that opens the session holds the requested scopes for this Source.

Merulan declares no LinkedIn scope, so the reach of the connection is the reach the aggregator negotiated.

Verification

Support-operated connection governs the LinkedIn connection. LinkedIn admits the aggregator rather than Merulan, and a re-sign-in replaces the handle on the same connection row.

  • Connect and map a Source runs the connect ceremony and binds collections once the credential is in hand.
  • Integrations lists every Source that carries a setup page, with its ceremony and verification posture.