I'm using Visual Studio 2017 to build ASP.NET Core 2.1 web applications. When a project is first created, there is an option to add authentication. I can add "work or school" single org cloud authentication at that point.
There is also an option to add authentication through the project "Connected Services" by selecting "Authenticate with Azure Active Directory". This option seems to add more (and different) code than the first way to add authentication.
When would I use one vs. the other?
Thanks in advance!
Related
Assume that there is an application, SPA, that uses Google OAuth2.0 to access the Google Drive API.
Reading the docs, the application flow seems familiar enough on the client-side specially with Google's JavaScript library for authentication. However, I have stumbled upon a roadblock during application registration phase.
When creating the credentials for our client application, I am redirected to fill out the form at the OAuth Consent Screen first. There, among other things it demands us to declare whether the application is in Testing or In Production phase, so it can decide whether the app will be available to everyone or to Test Users only.
Assume I create a project for our application and set it on testing at first and then change it to production once I am ready to publish (with a new set of credentials as well).
My question is this. What if development continues on the application for new features while one instance of the app is in production? During development and testing I would need to restrict the application to my Test Users alone. Since the OAuth consent screen is project specific, not credential specific, will I require multiple projects on the console for every environment in which the application is running?
As in,
Project MyAppTesting will permanently remain in testing mode and will denote our development/testing branch.
Project MyAppProduction is always in production and denotes my production branch.
Similarly for the mobile client:
A MyMobileAppDev project having credentials configured with the debug keystore hash
A MyMobileAppProd project having credentials configured with the production keystore hash.
(both sets of credentials share the same package name).
Is this the idiomatic way? I failed to find any documentation on the matter. Please advise.
What #JohnHanley stated is the best way and the best practice when deploying application/s in GCP.
You can create multiple projects and create different Oauth for each of the projects. Check out this link on service accounts.
In addition to that, there are also some pros and cons when it comes to billing.
Pros:
Users consider having multiple billing accounts with respective projects assigned for each account to be able to see their billing details separately. In this way you can monitor the billing for each of the respective projects for each account.
Cons:
Attaching all the projects to one billing account, however, the billing reports will show all of the sum of the cost for all the projects, but you can still use the filter menu to be able to see the charges for each project.
I am trying to integrate my magento v1.9 store with click & drop. But when I make connection it will show "Connection to your marketplace failed. Please check your details and try again".
For Magento 1 we found that being able to set the WS-I compliance solved this by making the Click and Drop system compatible with Magento API service.
Go to -
'System>Configuration>Services>Magento Core API'
and under General Settings change the WS-I Compliance from Yes to No.
Now your Magento API will be compatible with Click and Drop.
Works for Magento 1.x. No idea how to do it for Magento 2!
Make sure you have set up Magento API credentials correctly and all required resources have been allowed in selected user group
System->Web-Services->SOAP/XML RPC - Users
System->Web-Services->SOAP/XML RPC - Roles
Check SOAP PHP Extension is enabled for the PHP Version running on Server.
I have a WSO2 Axis2 Service project, that has a dependency on five other web services. I have generated the service with WSO2 developer studio 2.1, so the service is a maven project.
If I use the developer studio wizard for creating the axis2 client projects, the wizard creates the clients as eclipse projects, and not a maven projects.
I am thinking that it would be cleaner for me to create each client project from scratch as maven projects (using the wsdl2code plugin) rather than use the developer studio wizard. These five maven client projects can then be added as dependencies to the service project.
What is the best practise for managing the relationship between service and client code in WSO2 projects?
It depends on the use case. Developer Studio is really helpful for someone with limited knowledge to start with and also with its wizards you do not miss the steps that are essential in completing end scenario. But in your particular use case where you need to generate lots service stubs it will be easy to use Maven and automate client stub generation. In WSo2 we generate lots of service stubs and use Maven to automate that. .If you need more governance on that you can use some repository to manage WSDLs and then use maven plugin to pick wsdls from there. So whenever you change your service your client stubs will reflect those changes.
I have a problem for a few months now...
I have a web service and a client using the web service.
When i try to add the web service to the client(with "Add Web Reference.."), i search for web services on the local machine and finds it. but when i click it in order to add it to the project i get a prompt dialog asking me for username and password.
I recall times when i didn't have this dialog and I'm not sure why this happens now...
the Web.config file of the web service contains <authentication mode="Windows" />
Few details:
I'm using Visual Studio 2008 Standard.
the programs are written in C#.
I'm using IIS 5.1 and the web service configured only with "Integrated Windows Authentication" checked.
in my windows XP I'm using (in order to login) a user name and password.
No matter what i do to add the web Service to the client i can't add it. it fails.
Check to see if your web project (client) is running on vs2008's built-in web server... under Project -> Properties -> Web section.
If not, can you check those same settings on the web service project and try connecting with both options?
That should do it.
**from comments above
I would recommend that you check and see if you have the option NTLM Authentication checked under Project Properties -> Web. If you uncheck this option you should be able to add the Web Service without having to authenticate.
http://msdn.microsoft.com/en-us/library/aa378749.aspx
I am using WCF for the first time. I Have successfully created the service and it works fine on my local machine. I want to know the steps involved for deploying the service to the client environment (including changes to the config file, IIS settings) and any other miscellaneous settings.
http://msdn.microsoft.com/en-us/library/aa751792.aspx
There you go - the how to from Microsoft
Right click the service project in VS, select Copy Website.
Specify the IIS path. (may need to connect)
Moves / sync all files.
You can also deploy a WCF service to a windows service host. This is desirable in many situations which are outlined here:
IIS WCF service hosting vs Windows Service