I have a WebView in my Xamarin.Forms app. Followed instructions here to integrate AirWatch SDK into my iOS App.
I have also added an SDK profile to the IPA via AirWatch console. The profile has been configured to use AirWatch tunnel when accessing a corporate resource.
However, I get a 403 (Forbidden) response when trying to navigate to the URL.
Am I missing any setup?
Related
I found a lot number of examples how o do this.
https://learn.microsoft.com/en-us/aspnet/core/blazor/security/webassembly/hosted-with-azure-active-directory?view=aspnetcore-6.0
And it works fine when I run it locally in debug.
Everything is fine, until I want to publish the application up to an Azure APP Service.
I create an App Service and connect the server registration to it
I add on the client registration the URL of the APP Service https://xxxxx.azurewebsites.net/authentication/login-callback
In Visual Studio 2022 I publish the server application up to the App Service
To my surprise, the application does not work from the published site...
I get the response:
Sign in
Sorry, but we’re having trouble signing you in.
AADSTS700054: response_type 'id_token' is not enabled for the application.
I can not find an example that go all the way to a published APP service...
So what is wrong in my thinking here?
You need to register the app in Azure AD.
Your error message is: "'id_token' is not enabled for the application"
To fix this under Advanced Settings, Implicit grant check the box "ID tokens".
Hi all I am new to iOS development, I have put in the deep end to get push notifications. I found pushsharp and was using this tutorial
Tutorial I a using
I have used a windows application instead of web application and added the latest pushsharp. The code build and runs and I can get the push notification but only on sandbox.
I build my iOS app
Open the ipa on my iPad in xcode to install
once installed open the app and select allow to allow remote notifications
Get the device token when the app is opened and stick it in my winforms app
send a push using push sharp and bada bing bada boom it works like a charm.
I want to be able to use my production certificate as well. So I created a provisioning profile for App store. Created a signing request, created a certificate and in my provisioning profile section on apple portal i can see my new provisioning profile
I am able to build my iOS app successfully however when i try and install the ipa onto my ipad i get an error
App installation failed
a valid provisioning profile for this executable was not found
Is there a step which i have missed? Why do i get app installation error.
What will happen if I release a app which is using devcertificate to show push notifications?
You can't use a distribution provisioning profile to run the app on your ipad directly.
The iOS Distribution certificate can only be used to build an app that will be installed via the App Store.
You need to use either a development profile, or an enterprise distribution profile to install on test devices.
If you want to test a beat version, you can test the app using TestFlight.
Here are some way to test a beat version.
What will happen if I release a app which is using devcertificate to
show push notifications?
You have to use a production push certificate to push notification in release mode.
I am deploying a Java FX WebView app using Web Start. And I am having trouble authenticating with Google 2 Factor Authentication enabled.
However, It does work correctly for regular authentication (username & password only).
With 2FA: It sends me the Yes/No option to my phone, but once I click yes, the webview doesn't respond.
Now, 2FA in the webview does work when I run the jar locally. It only fails when loaded via Web Start.
The Web Start URL is:
http://aubreigo.info/java/FX-People.jnlp
And the Jar file is located:
http://aubreigo.info/jav/FX-People.jar
So to summarize:
[OK] Standard Authentication
[OK] 2FA running locally (java -jar FX-People.jar)
[FAIL] 2FA running in Web Start
I believe this is a bug in Web Start. Can someone report it?
I have reported this issue to Oracle as a bug with Java Web Start.
I programmed (on JDeveloper Studio) a custom page for Oracle Cloud Application R13 and it is working like a charm. I deployed my customization on my Oracle WebLogic Server but I couldn't help to notice the website I created was HTTP and not HTTPS when I opened it from Oracle Cloud Application. On top of that, I also noticed I could access this custom webpage from anywhere (using any device) without any security verification or login as long as I use the same URL with its token.
I would like to know how to make my custom webpage's url not being accesible just with its URL and also make it HTTPS instead of HTTP if possible.
WebLogic Version: 12c
Oracle Fusion Application version: 11.13.18.10.0
JDeveloper version: 11.1.1.7.0
I believe this might have to do something with the WebLogic configuration, since I tested the same java project on Java Oracle Cloud SaaS Extension and it doesn't have this problem. Whenever I try to open that webpage from any other device, it asks me for login credentials. I am currently working with Oracle Java Cloud. (it is not the SaaS extension version) that's why I have this problem.
Have you configured security for your application in JDeveloper? If not then your page and application is considered public and not private.
As for HTTPS, weblogic server uses 2 ports one for HTTP and an other one for HTTPS.
Regards
I have an Azure website (built using VS2015 Community) which uses "social" login for authentication.
I have successfully deployed a working PoC to azure which happily authenticates the user using the Google+ or Microsoft Account authentication services - i.e. the Azure app service is configured correctly to support social login from these two providers.
The problem is that I don't know how to replicate this for development on localhost; when clicking on one of these links (e.g. the MS one) the browser navigates to http://localhost:60380/.auth/login/microsoftaccount and I unsurprisingly get HTTP Error 404.0 - Not Found.
Question: is there a way I can configure my solution/local environment to authenticate using social authentication whilst running on localhost? Service providers such as Google seem to have no issue letting you specify localhost addresses.
My website has some very basic authorization checks that I want to perform, and I obviously want to do this on my dev environment first.
For your reference - HTML / Login links:
Microsoft Account
Google Account
Google API Manager Config - Authorized JavaScript origins
https://[my site].azurewebsites.net
http://localhost:60380
According to your description, I assumed that you are using Authentication/ Authorization of Azure App Service which provides you with an easy way to protect your application without changing any code on your app back-end.
As I known, when your app hosting on Azure then you could take advantage of the "Easy Auth" feature. But while developing locally, I assumed that you need to write your code to support "social" login for authentication. For more details, you could follow this tutorial.
Additionally, you could follow this Architecture of Azure App Service Authentication / Authorization and this tutorial for a better understanding of Easy Auth.
The integrated identity support is a feature of App Service that cannot easily be moved to localhost development. If you need to test locally on your dev machine, you'll need to simulate the identity component yourself.
If you are building a mobile app, there is some support for local debugging which might be helpful: https://github.com/Azure/azure-mobile-apps-net-server/wiki/Local-development-and-debugging-the-Mobile-App-.NET-server-backend
Otherwise, I suggest you create a second web app to use for integrated development/testing. It's not as convenient, but Azure App Service does support remote debugging, etc, through Visual Studio.
I've been battling through the same process. Feels to me like this is a gap - I'd love to see the .auth pipeline included as part of the dev environment.
Currently, I use this the method defined here - https://weblogs.asp.net/pglavich/easy-auth-app-service-authentication-using-multiple-providers, and whilst clumsy, it works for me.