|
1. The lounge is for the CodeProject community to discuss things of interest to the community, and as a place for the whole community to participate. It is, first and foremost, a respectful meeting and discussion area for those wishing to discuss the life of a Software developer.
The #1 rule is: Be respectful of others, of the site, and of the community as a whole.
2. Technical discussions are welcome, but if you need specific programming question answered please use Quick Answers[^], or to discussion your programming problem in depth use the programming forums[^]. We encourage technical discussion, but this is a general discussion forum, not a programming Q&A forum. Posts will be moved or deleted if they fit better elsewhere.
3. No sys-admin, networking, "how do I setup XYZ" questions. For those use the SysAdmin[^] or Hardware and Devices[^] forums.
4. No politics (including enviro-politics[^]), no sex, no religion. This is a community for software development. There are plenty of other sites that are far more appropriate for these discussions.
5. Nothing Not Safe For Work, nothing you would not want your wife/husband, your girlfriend/boyfriend, your mother or your kid sister seeing on your screen.
6. Any personal attacks, any spam, any advertising, any trolling, or any abuse of the rules will result in your account being removed.
7. Not everyone's first language is English. Be understanding.
Please respect the community and respect each other. We are of many cultures so remember that. Don't assume others understand you are joking, don't belittle anyone for taking offense or being thin skinned.
We are a community for software developers. Leave the egos at the door.
cheers,
Chris Maunder
The Code Project | Co-founder
Microsoft C++ MVP
modified 16-Sep-19 9:31am.
|
|
|
|
|
Watch how CoPilot does this: GitHub CoPilot X in Visual Studio - YouTube[^] ... Now, if only users would pay...
Graeme
"I fear not the man who has practiced ten thousand kicks one time, but I fear the man that has practiced one kick ten thousand times!" - Bruce Lee
|
|
|
|
|
I've been retired for a few years now, but I've recently been contacted by an organization that wants me to consider going back to work for a while. They run a large facility using diesel generators and, as you can imagine, it's not cheap. They want to expand into solar with storage and integrate it with the existing system going forward. There is also a likelihood of expanding to take on a few small towns, as well. It's been suggested that I would be the right candidate for managing the effort. This is very preliminary, but I'm doing a bit of research anyway.
Years ago I tried using several project management software packages, all of them pricey, and for the most part, more work to maintain than they were worth. Pencils and butcher paper on the wall were far more efficient. I've tried several times over the years to use, especially, MS Project, but it is among the worst I've seen and now it's outrageously priced, as well. Has anything been developed in the past dozen years or so that can handle a relatively large project and a reasonable price? And suggestions would be welcome. Mind you, this is not a (primarily) software project, though there will be a systems/ SCADA component in the solution. Thank for anything you can suggest!
Will Rogers never met me.
|
|
|
|
|
|
Good question, and an important distinction! This would be a division manager position, probably with multiple distinct projects, defining and prioritizing tasks, assigning resources, and tracking critical path progress. I'd love to ditch the personnel management side, but that's probably going to be unavoidable. That can be handled with other software... Think $100 million+ capital project range, with multiyear scheduling and tracking.
Will Rogers never met me.
|
|
|
|
|
Sounds like you need to find out what they're already using for this type of work.
|
|
|
|
|
I have much yet to learn about the position, but I will be surprised to find that they're using anything more capable than Excel, and that badly. We shall see.
Will Rogers never met me.
|
|
|
|
|
|
I've used MS Project and some others. I got it / them all to do what I wanted (plant scheduling; software; capital budgeting; pipelines). They all do it a bit different; you improvise; a resource is a resource. There are legitimate sources of discounted licenses for MS Project; and it's a business expense.
If you program, it also means you can access its object model (MS Project); export / import Excel, Access; etc.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
|
|
|
|
|
|
|
#Worldle #433 1/6 (100%)
🟩🟩🟩🟩🟩🎉
https://worldle.teuteuf.fr
easy one
"A little time, a little trouble, your better day"
Badfinger
|
|
|
|
|
Hi all,
I have a question based on the below hypothetical scenario.
I have an Azure based system comprised of:
Web app (Blazor)
Multiple Azure functions
A set of C# library NuGets written to support shared code
Azure SQL
Internal-only APIM
External APIM (for mobile apps and third Party subscriptions)
Azure Front Door
Various Azure services, like Key Vault, Azure Storage, etc.
ADO DevOps (incl. ADO Git repos, not GitHub, pipelines, artifacts, testing, etc.)
ADO Boards for case management
Developers use VS 2022 with access
Secure information that apps use like keys, usernames/passwords, etc. are stored in a key vault.
Now, for the question. What process do you recommend for the apps (not directly publicly accessible other than port 80 HTTP for the web UI) to access the key vault without leaving any keys in config files that could be compromised?
I know what I think, but if I knew everything 100% correctly, I probably wouldn’t be here. 🙂
Thanks in advance.
|
|
|
|
|
In a domain? Doesn't Azure use SQL Server?
We have some data encrypted in SQL Server, with keys and certificates, etc.
Only a user authenticated on the domain with access to the SQL Server database with access to the keys and certificates can decrypt the encrypted values.
|
|
|
|
|
That is certainly a common practice.
Where is the username and password stored for the user you mentioned?
If the app uses that type of user login, doesn’t it have to get the username and password from somewhere outside the DB?
|
|
|
|
|
The domain performs authentication for the user.
The user provides the username and password to the domain.
|
|
|
|
|
And the user can share their password, have it hacked, etc. Still not secure.
|
|
|
|
|
As has always been the case. The user has to know his/her password and might write it on a sticky note or something. That can never be fully secure.
Consider a building with many doors and the janitor has copies of all the keys, locked in a box. But the key for that box can't be in the box, it has to be somewhere else, usually in the janitor's pocket. If that one key gets stolen, the thief has access to all of the other keys.
The janitor can lock the lockbox key in another box, but then the key to that box might get stolen.
It's never-ending. There will always be some nth item which might get stolen and may then provide access to all of the other items like dominos.
I have no idea how someone can possibly think that anything can be fully 100% secure. The concept is a fallacy.
|
|
|
|
|
Not 100%. Just reasonably secure. That is why Azure (and I am sure AWS and others) have the kind of authentication that doesn't require an app storing the means of authentication.
|
|
|
|
|
Have the app read from the key vault when it starts, and then cache the value.
You don't want to constantly read from the key vault, as it is not a high throughput service.
|
|
|
|
|
And by what is the app validated to the KV, and where is that stored outside the KV where the app can access it?
|
|
|
|
|
 this is what chatGBT has to say :
Quote: To securely access the Key Vault from your applications without exposing the secrets in config files, you can leverage Azure Managed Service Identity (MSI) feature.
Managed Service Identity (MSI) is a feature of Azure Active Directory that provides Azure services with an automatically managed identity in Azure AD. With MSI, Azure services can authenticate with other Azure services that support Azure AD authentication, without requiring you to manage any secrets or credentials.
The process for accessing the Key Vault using MSI can be summarized in the following steps:
Enable the MSI feature for your Azure App Service/Web App: Enable the system assigned identity for your Web App by turning it on in the Identity blade of your Web App.
Add access policy to Key Vault: Once MSI is enabled, navigate to your Key Vault, select the Access policies blade, and add the necessary permissions to allow your Web App to access the Key Vault.
Modify your code to use MSI to authenticate with the Key Vault: In your code, you can use the Azure.Identity NuGet package to authenticate with the Key Vault using the MSI endpoint. Here's some sample code that demonstrates how to access a secret in a Key Vault using MSI:
var credential = new DefaultAzureCredential();
var client = new SecretClient(new Uri("https://{keyvault-name}.vault.azure.net/"), credential);
KeyVaultSecret secret = await client.GetSecretAsync("secret-name");
string secretValue = secret.Value;
|
|
|
|
|
Someone trained the AI bot well. That is what I do when I design the system. I find that "in the wild", a lot of shops don't.
|
|
|
|
|
Maybe you shouldn't hide the key, just encrypt it. The apps should know where the keys are and how to decrypt them.
As a real-world example, I need the ability for hundreds of customer desktop apps to be able to utilize one or more FTP resources, and also need the ability to change the credentials for those resources 'on the fly'. Those credentials are actually stored on a publicly accessible website in an XML file with very unassuming names/tags and, of course, encrypted. My 2 cents.
"Go forth into the source" - Neal Morse
"Hope is contagious"
|
|
|
|
|
I have done that before, but the issue still remains that the decryption key for that still has to be accesible to the app. And thus, accessible by another person.
|
|
|
|
|