Skip to main content

Really simple Authorisation Header for lots of @External Services.  

Password Authentication Named Credentials will always encode the username:password.

It would be ideal if the username field was not mandatory so that just the password is encoded to create the encodedkey for the Authorisation Header.

 

Any way to do this declaratively?

 

#Enhanced External Services #Named Credentials

4 Antworten
  1. 7. Sept. 2022, 15:28

    Thanks @Ross Belmont - this is EXACTLY what is needed to unlock the potential for External Services.   This is a game changer for no-code / low-code pioneers. Thanks!!  

     

    We have 3 services we wish to integrate using this Custom Protocol capability and I'll let you know how we get on.  Thanks again.   S

0/9000