I’m a beginner engineer, all I want to know is how we can integrate biometric authentication to existing projects. I’m aware of the biometric authentication process and tried as an example and it worked out . Please show me a way to find this one. I’ve searched many websites related to this, but couldn’t find anything. I’m supposed to know how we can start with biometric login without prompting a biometric icon or something that is I need to login whenever I touch the sensor while the app is opening. And then after successfully login, how can we be redirected to the home page using the URL in android studio. Your time and efforts will be appreciated. Thank you
Related
I have recently started using the SAML Python toolkit (Flask) from OneLogin. I have a problem in that when I sign out of the application itself, it does not sign out of SSO so that the application can be re-entered into with existing login credentials stored in SSO. Is there anything that you can suggest I can look at to help solve the problem? Logging into the application is no problem, just when logging out, SSO still retains the details. Is there something in settings.json I need to do further?
I can force it to SSO to fully log out but only by force, it does not do it automatically.
What is the difference between singleLogoutService for the sp and singleLogoutService for the idp?
Any other aspects of the settings.json file that I can check over / alter?
Thank you in advance.
Andrew
I've wrestled with the same problem myself. From what I learned, its possible to setup a logout functionality which you can then add to your settings.json. However, this requires SAML2 to be configured in a certain way in addition to that if I recall correctly.
The solution I came up with for now is to have a logout page which deletes the session data via "request.session.delete()". However, in order for this to work, the user then has to completely close his/her browser afterwards. Therefore, this command is perhaps best displayed on a webpage that says something like, "You have been logged out, please completely close your browser to properly end your session."
I have been banging my head against a wall for the last two weeks. I'm trying to set up a contact me web page for my business. Having read all the warnings about mailto, I opted to use phpmailer for this. Similarly, I decided to use XOAUTH2 for sending the mail through gmail. I found several sites, including instructions at the phpmailer github page, that should have walked me through doing this.
Here's where I run into problems. After logging into the Google developer console, creating my project, and enabling the gmail api, all of the sites that I found talk about creating my new client ID. Every single one of them tell me that I will get a simple pop-up where I click that I want to create a web application, fill in a few items, and voila, out will pop my ID. When I did this, however, I was required to complete the consent screen before I could do anything else, and these screens did not match anything that was shown on the web sites I used as a guide. I muddled through as best I could and did finally get a client ID (I think/hope).
Does anyone know of a site or sites that walk a person through this in a way that matches what the development site actually displays? Did Google recently change things and the help sites haven't caught up? Having to guess at some of this is definitely not the way to do things. I'll be testing the results in a couple of days, but won't be surprised if things don't work right. At that point, I'll probably need more help to figure out what went wrong.
Thank you for listening to my rant.
I've created a Bot in MS teams that can authenticate the user against AAD. I've used the AuthBot code for this.
This works correctly. I have questions regarding further improving the sign-in experience. The Bot currently opens up a web browser, the user logs in and is redirect to a page with a magic number that he or she needs to copy-paste back into teams.
If I understand the Authentication section on this page correctly, then the following should be possible:
The browser window can be opened inside of Teams instead of through
the browser by specifying a validDomains attribute in the Teams
package manifest file. However, I chat with the Bot 1:1 and it
doesnt seem to use the manifest file (the Bot's image doesnt use the
one from the manifest). How do I get the login window to open inside
Teams?
There is a MS Teams javascript file. Can I use this (on the page that my Bots shows after authentication) to
redirect the user back to teams, and possibly automatically paste
the magic number into the chat with the Bot?
We missed answering this in August, apologies.
A more elegant way of doing bot authentication has been a common developer request. We are almost ready to publish samples and documentation for this solution once it's fully deployed on all client platforms. This approach removes the need for AuthBot completely and supports an integrated authentication experience, i.e. without opening a browser tab.
Currently, however, to answer your question, there is no way to have an inline authentication experience and the validDomains is not enforced (since it's just opening a browser page). The JavaScript client SDK you refer to is not used at all with bots because bots cannot currently run code on the client.
So in other words, what you are doing with AuthBot is currently the best possible way to do it.
Does anyone know why my action can NOT use in web simulator??
I set my invocation name for testing as "test", and in web simulator , I try to use my action by input "Talk to test", but it told me "Sorry, this action is not available in simulation"...
Is there anything wrong with me ??
I got this to work by saying "talk to my test app" or typing it in to the simulator prompt, that triggered my app to start in the simulator. I am using an account that is NOT associated with a home device, I also have NOT entered in artwork etc.
I have found that you have to type in that phrase anytime the simulator gets confused to get back into your intent flow.
In my case it looks like this in the Dialog portion of the simulator:
Turns out for me, even though I had turned on all the activity controls as the tutorial instructed, the organisation my login was associated with had them disabled.
Ask your admin to enable "Web & App Activity" in "My Account" > "Admin" > "Google Services"
I had same issue. This is how I "solved" it
Registered Google Home physical device to my email used for Action and api.ai development
(Redeployed, now Silly project started working)
(Still my project won't work)
Changed the invocation name to something simple ( My first language is not english)
Now Web simulator started working(
One possible Root cause - you are logged in via your second account.
This is the same issue I had. The UI from the earlier google home tutorials have been changed a bit. So after clicking the actions on google in api.ai we are redirected to to actions on google page. (Previously it was sent to the web simulator straight)
I created a project called personal butler in api.ai but what I saw was a project called API project, so when I clicked it and try to simulate it I got the exact error.
I registered to api.ai from my secondary google email. So when I was redirected to the actions on google page, it logged in via the primary account. After I signed out and loged in via the same account I was able to see my project and it was working fine.
PS - When testing with google home also the same account should be used in the andriod app
This bug should be resolved now. If you are still having this problem, you should try pairing your account with an actual device first. The issue was resolved for me by signing in to the Google Home app on my mobile device and pairing it to a home unit. After that, using the simulator then works in the browser.
Is there a way to reboot the phone using c# code from an Universal App?
I could not find anything in the github UWP samples library.
UWP apps/Windows Store apps have very limited access to system method/resources - by design due to security issues.
There is no way to reboot the phone with official API.
You can try to find some hacks to do it - I've seen once some methods (don't have links now) using Pinvoke in WP8.1 - but you cannot be sure if they will work and/or pass certification.
Except that you cannot do it, you should not reboot the system from code.
Even (most) OS procedures ask user permission, all you can do is prompting the user asking for a reboot.
Also, you shouldn't need a system reboot. At most, what you need is an app restart. I looked for an "APP restart" API but I couldn't find it, but what you can do is closing it.
You should tell the user that the app will close, and doing so after the user confirmed invoking CoreApplication.Exit();.
The user then can reopen it.