Allow use NamedCredentials in client side (LWC, Aura, etc) - Ideas - Salesforce Trailblazer Community
Trailblazer Community

All Ideas

Idea Details

Post an Idea
190  Points
Open
Idea has been posted. Give it an upvote or downvote.

Allow use NamedCredentials in client side (LWC, Aura, etc)

Development (Apex, LWC & VF)

Would be nice to allow developers to use NamedCredentials on client side API calls (for example in fetch). This will allow developers to bypass current Apex limitations for big payloads or files, for example when trying to upload an user's computer file to an external service via REST API.

This will allow developers to mantain user's external credentials/tokens secure and remove the need of storing this credentials in CustomSettings and/or Custommetadata, while simplifying auth process

Below a proposed example in a LWC
 
//other imports here...

import { endpoint, OAuthToken } from '@salesforce/namedcredential/<MINAMEDCREDENTIALAPINAME>

class myComponent extends LightningElement {

    myApiCallMethod() {
        fetch(endpoint + '/my/service/slug', { headers: 'Authorization' : 'Bearer' + OAuthToken})
            .then(res => {
                //process response
            })
    }
}
Also will be possible to export a function to hide token in client side. Some thing like:
 
//other imports here...

import { apiCall } from '@salesforce/namedcredential/<MINAMEDCREDENTIALAPINAME>

class myComponent extends LightningElement {

    myMethod() {
        apiCall({
            headers: {
                'Customheader': 'value2'
            },
            method: 'POST',
            body: {
                mydata: 'mydataValue'
            }
        }).
        .then(res => {
            // process response
        })
    }
}
Best regards!
 

Merge Idea · Flag

  • Upvotes
  • Downvotes

Ideas

Apps

from AppExchange

Questions

No results found.

Help us to keep IdeaExchange clean by pointing out overlapping ideas. We'll investigate your suggestion and merge the ideas if it makes sense.



 

 

Thanks for your merge suggestion. We will review it shortly and merge the ideas if applicable.

Salesforce takes abuse situations very seriously. Examples of abuse include but are not limited to posting of offensive language or fraudulent statements. To help us process your request as quickly as possible, please fill out the form below describing the situation. For privacy and security reasons, the final outcome of an abuse case may not be revealed to the person who reported it.


 

Thank you for your feedback. We take abuse seriously and will investigate this issue and take appropriate action.