I have an ASP.NET Core Web App service and I want to offer small custom websites to my customers. (like my own version of GoDaddy)
Customer's domain -> SomeCompany.com
is forwarded to my site -> mysite.com/customer/123
Is it possible to retain the customer's domain in the browser URL, and not show my site and route info? What would have to be in place to do this?
Thanks!
Simple forwarding from the domain provider just results in the customer's URL being replaced with my full URL.
Related
I have a web application which runs on one server, but multiple domains (like ab.c, a-b.c, ab.d, a-b.d etc.) are pointed to this application. I would like to use other systems' (e.g. Google, Facebook, Microsoft) authentication. Google and Facebook are working fine, but it looks like Microsoft Live allows only one domain per application. Is that correct? If yes how to handle this? Does it exactly means I have to create separate application on MS developers site and I have to choose different Client ID for authentication based on user's referrer?
I have an iOS app that communicates with a web service, this product will be licensed to customers for their employees. Each customer will have to install the web service on their own server and provide an IP/URL for the iOS app to communicate with. Right now, the web service URL is coded in the app. I won't know the customer's web service URL before giving them the compiled app.
I don't know enough about enterprise distribution to know how to do this. Do if I need to compile the app for each new customer with their specific web service URL, then give them the app? Or is there is another way this should be done? I was thinking a plist file or manifest that can be configured with the URL but I'm not sure. How do they update that and get the app to use that? I had a developer make this app for me and they said the URLs shouldn't be in manifest/plist files.
I can't find any information about this on the apple developer site or on this site.
You can just add text field in your app settings or at the start where user can define its server URL like www.abc.com For all your customer rest of your path (webservices/yuorservice or what ever you use)will be same . Then you get this url and save in your user defaults to use it for the future for that user.
Using this approach you only need to compile app one time for all the customers.
App has no knowledge of manifest file
Your developer is right--you should not include any app-configuration information in the manifest file, since the app has no knowledge of the manifest file or web page that it was downloaded from. Here is a link to an answer I gave regarding this topic.
Enterprise deployment rules
Apple only allows enterprise deployment internally within a company. So, distributing an App through your enterprise license to multiple companies is prohibited.
Approach
I can think of one option that might work for you, given that you have a URL that should change for different customers.
This assumes that you will employ a login.
Devices
Your login web service response to the device can include the URL that is configured for that customer. This URL can be one piece of data inside a configuration file in JSON format.
Web Server Admin Page
You can optionally employ an Admin page, also accessible through login, where your customer can set the URL, and any other settings. The advantage of including an admin page for your customers is that they are able to manage the product on their own, without the need for additional product support.
I am trying to connect to VSO using oAuth.
First step is to register our app and configure a call back url.
I am creating a console application to test the connectivity.
Please let me know how to configure the callback url.
Firstly, please take note that: Right now, it is only supported to register web application, it is impossible to register a console app.
So, you need to have a web app first, you can download and use this sample project for a quick start: https://vsooauthclientsample.codeplex.com/
After you download the app, open it in VS2013 or higher, right-click it in Solution Explorer and select Publish.
On the Publish Web page, select Microsoft Azure Website option to publish that web app to Azure.
Then, the web app is published to Azure with the URL similar to: https://vsodevabc.azurewebsites.net
And when you register this web app, you can set Application Website and Callback URL to be the followings. (note: the callback URL should be https://yoursite.azurewebsites.net/oauth/callback, where "yoursite" is the name of your Azure web site)
When using VSO (now called Team Services) with oAuth2.0 you do have to provide callback url endpoint that Microsoft's Team Services can call directly. So you need to have your application's callback url endpoint published such as publishing to Azure or Aws or any hosting provider that will allow you to have publically accessible url. In the FAQ under Team Services Rest API, there is mention of this approach for debugging purposes:
Visual Studio Team Services does not allow localhost to be the hostname in your callback URL. You can edit the hosts file on your local computer to map a hostname to 127.0.0.1. Then use this hostname when you register your app. Or, you can deploy your app when testing to a Microsoft Azure website to be able to debug and use HTTPS for the callback URL
Visual Studio Team Service's Rest API oAuth
Background
Our customer wants their ASP.NET MVC application to use Yammer as authentication, and integration with comment-fields on the webpage. In other words, when you enter the site for the first time, you click "Sign-in with Yammer", get redirected to Yammer login, allow the App access, and there you go. For this, the customer has created an external Yammer-network, so that everyone who's a part of this network, has access to the site. This should also work for external consultants, not in our customer's home network, but in our customer's external network
The App is registered in our customer's Yammer-solution (home network), and deployed.
The problem
People from our customer's home network, who also are included in the external network, has access to the site. The way we do this is to first get the user's access token (for the home network), then do a look-up in the /api/v1/networks/current.json endpoint to see if he is in the correct external network, then use the /api/v1/oauth/tokens.json endpoint to get the access token for that specific external network.
This works fine for end users from inside the customer's home network. However, for external clients, this does not work all too well. It seems that when trying to authorize towards an App registered in a different home network than you, the authorization code you get back in the OAuth-dance, is invalid. So you'll not be getting an access token, and hence can not get the access token for the external network.
I've looked into an endpoint used by the client-side OAuth flow which is https://www.yammer.com/dialog/oauth?client_id=[:client_id]&redirect_uri=[:redirect_uri]&response_type=token. When I fill in the App info (clientID, redirURI), I get redirected to the login-page, then I get redirected back to the redirURI, and then I have the access token in the URL. Since I'm doing all this authorization from code behind using the OAuth2Client, it seems I'm basically using the same endpoint, but with &response_type=code, to get the Authorization code, and then use that together with client ID and client secret to get the access token.
Is it possible for me to get the access token at all, from outside of the home network the App is registered in?
If anyone has anything to add to this it would be greatly appreciated. I've been stuck quite a while now.
If I left something essential out, please let me know so that I can edit it in. Thanks.
Yammer users are identified by their organisation email address. If I'm from microsoft.com then my home network and external networks are all tied back to this domain. Users in an external network may have one of domains, but when it comes to identity all of that is handled by the home network. In your case you have company.com and possibly a very long list of consultant1.com, consultant2.com domains. These all authenticate back against their respective home networks, and possibly use custom SAML identity providers that you shouldn't need to care about.
By default, apps are tied to their home network which means that users from other networks can't authorize it. The normal way of globalizing an app is to publish it to the public App Directory from within the customer's app settings page. It may be possible to achieve this via a tech support case with Yammer Support at Microsoft. It will probably take some time to get this completed though. It may be best for your customer to open the support case because it's their network which will have the app associated.
I'm trying to create a web service for my college, which uses Google Apps for education. We have our own themed login page. I was wondering if its possible to use oauth/ openID to use our Google apps account to log in. I know when I use generic oauth, I can enter the school email address and force it to take the Google apps domain, but is there a way to redirect to it directly?
You can use the hd parameter in the oauth request to specify a google apps domain to login through. I believe the apps domain needs to have the option enabled and/or be a paying domain, but I am not certain about this part
Example URL
https://accounts.google.com/o/oauth2/auth?access_type=offline&DOMAIN.COM&response_type=code&redirect_uri=http%3A%2F%2Flocalhost&scope=https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fuserinfo.email%20https%3A%2F%2Fwww.googleapis.com%2Fauth%2Fcalendar&client_id=CLIENT_ID&type=web_server