You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Yes. I can contribute for this issue independently.
Non-technical Request Proposal
Issue Description:
Background:
I am using the Feathr project to integrate with Azure services, and I need to configure the client with sensitive Azure credentials, such as Azure AD secrets or connection strings. However, I want to ensure that these credentials are not exposed in plain text within the Feathr client configurations to maintain security and prevent unauthorized access to Azure resources.
Question:
Is there a recommended best practice or approach for configuring the Feathr client in a way that allows me to use Azure credentials without exposing them in the client configurations? I want to ensure that end users of the Feathr client do not have access to these sensitive Azure credentials.
I'm open to any suggestions or guidance on how to securely handle Azure credential management within the Feathr project.
Currently from what I see every end user that uses the feathr client needs access to an ADLS key, client secret, and potentially other config items, that if exposed could give the user direct access to these resources.
Thank you for your help!
The text was updated successfully, but these errors were encountered:
Willingness to contribute
Yes. I can contribute for this issue independently.
Non-technical Request Proposal
Issue Description:
Background:
I am using the Feathr project to integrate with Azure services, and I need to configure the client with sensitive Azure credentials, such as Azure AD secrets or connection strings. However, I want to ensure that these credentials are not exposed in plain text within the Feathr client configurations to maintain security and prevent unauthorized access to Azure resources.
Question:
Is there a recommended best practice or approach for configuring the Feathr client in a way that allows me to use Azure credentials without exposing them in the client configurations? I want to ensure that end users of the Feathr client do not have access to these sensitive Azure credentials.
I'm open to any suggestions or guidance on how to securely handle Azure credential management within the Feathr project.
Currently from what I see every end user that uses the feathr client needs access to an ADLS key, client secret, and potentially other config items, that if exposed could give the user direct access to these resources.
Thank you for your help!
The text was updated successfully, but these errors were encountered: