I've seen other questions here about PNS, in terms of code, but how does the concept work?do I need to tell my client that they need a server? What goes in the server in terms of configuration/cron or whatever?
Please explain the process. Thanks a ton.
EDIT:
Please explain: Do I need to purchase an SSL certificate, or does Apple issue a "client" or " app" SSL certificate for me?
Yes, they basically will need a server. The steps go something like:
User installs application
Application asks for notification
Phone talks to APNS, registers for notification for that app and gets a token back
Application talks to your server to tell it the token
The phone keeps a connection open to APNS to listen for notifications
Periodically your server polls APNS for feedback, e.g. that the device has been disabled or the application has deregistered
When you have a notification, your server tells APNS, and APNS tells the phone, which displays the notification
Note: you download the SSL certificate from Apple provisioning portal.
Related
I've been using Firebase for a while and have successfully used it to verify phone numbers in past projects.
Now I'm trying to implement it completely on the backend because at my current project the end user (phone app) doesn't have internet access but the backend (the user is connected to) has.
My plan was:
The user is entering their phone number and sending it to my backend
The backend should send the phone number to firebase and send the client an SMS with the verification code
The client enters the verification code and sends it to my backend to verify
I wasn't able to find this and I'm not sure if it is supported. Any hints?
Firebase Auth does not support this. The APIs are driven from the client app, which is always where credentials are established.
If you need a way to verify a phone number only from a backend, you'll need to use another service. I'm sure you can find some using a web search.
you can use it as front-end third party login service like sign with google etc... with use of link
We are using BizTalk Server 2016 and I installed Future Pack 3 to test the Office365 Outlook Email adapter. I wanted to create a send port and select this adapter. I press the configure button to configure adapter and in this panel, I pressed sign in button to enter my credentials. But nothing happens when I press sign in button, No frame no popup. Do you have any idea?
To use Office 365 Adapters, install BizTalk TMS.
BizTalk Server TMS is a service that refreshes the Office 365 OAuth tokens used by BizTalk. It refreshes these tokens periodically, ensuring that the tokens always remain valid. It has a dependency on Enterprise Single Sign On service (ENT SSO), and must be installed on a computer that hosts the master secret server.
Please go through this article - https://learn.microsoft.com/en-us/biztalk/core/office365-adapters
As mentioned by someone in the comments. I recreated this in my local machine and first just installed the Feature Pack 3. If I only do that, the behavior mentioned in the post was recreated.
Then I installed BizTalkTMS and it resolved the problem.
https://learn.microsoft.com/en-gb/biztalk/core/office365-adapters
One further thing that will prevent the button from working is if the server has not been configured to use TLS 1.2 in prefrence, this will also silently error.
As per BizTalk Office365 email adapter not doing anything when sign-in button is clicked
And as perarticle it links to BizTalk Server Logic App Adapter: An error occurred while making the HTTP request. This could be due to the fact that the server certificate is not configured properly with HTTP.SYS in the HTTPS case you need to make sure TLS 1.2 is enabled and SchUseStrongCrypto enabled in the registry keys
The User setting up the the port also needs to be a SSO Administrator, otherwise that will throw an error (in the Windows Events).
I built an OAuth 2.0 server, and I had verify the implementation of the custom OAuth 2.0 server by postman in chrome, and an nodejs oauth client. It works.
My question is, when I launch Amazon Alexa app in android, and enable the skill. The login UI disappears. It shows nothing. So, I cannot login to get back oauth accessToken.
I use Facebook OAuth service instead now, it works fine. But I still need the custom OAuth 2.0 server to be workable. I doubt it's self-signed SSL certification now, and I will check it in these days.
Any help will be appreciated.
For Self-signed SSL certification, it doesn't work. With a trusted SSL certification, the login UI shows.
Conclusion
After many tests, the custom OAuth 2.0 server for alexa service, must meet following conditions.
The ssl certificate MUST be signed with trusted organization.
The https port MUST be 443, not a custom port. (Ex: 12345)
In some android mobiles, a self-signed certificate or a custom port, the login UI will display. But they all failed at another step for accessToken. The step for authorize is not a problem, but step for token seems to be blocked by alexa app. I suppose alexa app will check the port number, and it doesn't trust self-signed certificate.
I'm trying to authenticate login of a web app with three elements:
Userid of web app
Password of web app
Client Certificates installed on user's PC. I see a client or machine certificate as a long string or key which is stored in Windows registry.
I'm planning to put those three elements together in a table, so when user intent to login, it will send those three elements to server side and they will be checked.
For example, if user loads web app in a PC which has not be assigned to him, then server will validate that userid and password are correct, but client certificate does not belong to user, and will reject login.
I haven't yet installed a client or machine certificate in every client PC nor installed a CA in IIS. But according to Microsoft, an asp.net web app will send automatically a client or machine certificate to server and asp.net can get it. Also I have found another program example for doing that.
How is that possible? I allways thought that an asp.net web app can't read client resources and if you want to read client resources, then you should use something like ActiveX with all its complications.
Your are right, ASP.NET can't read any client resources. ASP.NET has nothing to do with getting a client certificate from the the user's PC.
What you do is to tell your Web Server (IIS) to request or require a client certificate. The server is adding a special http header to tell the browser to send a client certificate. The Browser asks Windows for one, or uses its own store (Firefox). The browser then sends the public part of the client certificate to the server.
Your ASP.NET can ask IIS whether the browser has sent a certificate and access that information for authentication purposes.
I have my spring web application hosted on AWS. After user signup it should send email to given email. But i can see that its not sending any email.
I am using a gmail account as sender of email.I don't see any exception or error also in my log.
You can check the ports, iptables(firewall),
Try sending a test email from the prompt/Bash.
for testing Linux
for testing Windows
If success, with the test, then work on the application.