better to use linkedin's updated /authenticate path so if the user is logged into linkedin and already has an active access_token, a redirect will happen without asking for permission again.
Can change the name of the methods to authenticate and change the spec tests accordingly later.
better to use linkedin's updated /authenticate path so if the user is logged into linkedin and already has an active access_token, a redirect will happen without asking for permission again.
Can change the name of the methods to authenticate and change the spec tests accordingly later.