Named Credentials: Securing and Simplifying API Callouts

[@strandboy23]

Really great review. I was extremely excited to use this as it appears to be exactly what I needed. Then I spent HOURS debugging what I believe to be a major salesforce oversight. Has anyone run into the 100 char limit on the consumer secret? I almost can't believe it and I can't find anyone else raising issues with it. I'm working with a 3rd party REST API that generates client secrets (consumer secrets) that are longer than 100 characters (but still within the 256 stated limit according to oauth 2.0). What's even more unbelievable is that it appears that salesforce got consumer key and consumer secret backwards as the char limit on consumer key (aka client id) is 256. Unbelievable. I have tested this and verified that it is causing the oauth to fail and I can see that the client secret is truncated. I know this is not the video creators fault but thought I'd raise it here to see if anyone else reviewing this video has run into the same issue. Again, thank you - really great overview.

[@niravkumar6261]

You got any solution for this?

[@strandboy23]

@@niravkumar6261 I submitted a change request to my engineering team at HOVER to shorten our consumer secret to less than 100. They made the change and everything works

[@ramanrajsaxena4423]

It's simply awesome. Very well explained.

[@alanpatric2218]

you show'ed with google credentials, but what about proprietary API's with OAuth2, refresh and login tokens?

[@VitaliiKondratiev]

Really cool, but how to check Authentication Status from APEX ?

[@anvesh4646]

very useful video!