Does SNS support token based connection to APNs?
I see the AWS documentation on certificate based connection to APNs, but don't see any way to connect via tokens.
Is this available? If so, is there any AWS documentation on this because I can't find it.
Currently (i.e as of 07th March 2020) Amazon Simple Notification Service (SNS) doesn't support Token Based Connection (.p8) to APNs
I would like to refer you to another AWS service called Amazon Pinpoint which I know support Token Based Connection (.p8) to APNs.
SNS now supports token-based authentication for APNs, using .p8 files. You can find more information about it here: https://aws.amazon.com/about-aws/whats-new/2021/11/amazon-sns-token-authentication-api-mobile-notifications/
Related
I found this article that describes configuring to use the AWS VPN Client.
https://aws.amazon.com/blogs/networking-and-content-delivery/authenticate-aws-client-vpn-users-with-saml/
Our team is currently configured using the OpenVPN Client and we would like to keep using it -- (OpenVPN Client is so much better)
The issue seems to be where we Add the Application to OKTA. Our OKTA guy tells me there is no option to add OpenVPN as a client and that there is no "OIN template" to allow this.
Is there a solution to this problem ?
I have functioning AWS Client VPN that authenticates with Okta.
I contacted AWS support and was told that SAML/Okta authentication only works with the AWS provided client.
I am trying to connect to IBM MQ running on cloud using REST API. I started with the documents link1 and also refereed link2 but looks like these document talk about on-prem instance of IBM MQ. I generated LTPA token and when i execute send message API, i get below error with 403 http error code. I understand that here the user i am using has no proper rights. I am not getting any documentation which explain how i can configure the user roles for IBM MQ running on cloud. Anyone has tried it and can shed some light ?
"explanation": "The authenticated principal is not authorized to perform the requested REST API operation.",
"message": "MQWB0103E: Not authorized to put to 'queue1'.",
As #habercode states your starting point should be the "Invoking the queue manager REST APIs" documentation For IBM MQ on Cloud - https://cloud.ibm.com/docs/mqcloud?topic=mqcloud-mqoc_qm_rest_api
As the doc states you will need a MQ username and API key to authenticate.
Get your MQ username and API key from your service instance in IBM
Cloud, then ...
base64 encode the combination, before using it with basic authentication.
Once you can authenticate, you can use the REST API documentation to configure your API calls.
We have a windows service that collects mail from via an imap connector and then processes that email and attachments into a database. Is there a way that we can do this using OAuth2 when exchange online removes support for basic authentication? There is no user interface to the service or user access to teh system when it is running beyond the start and stop of the service.
We are currently using Chilkat's excellent Imap component.
Yes, Microsoft have finally released support and documentation for this in Exchange Online. See the following Microsoft document:
Authenticate an IMAP, POP or SMTP connection using OAuth
I am working in IVR team. I write SOAP web services, write java client to access those web services and set data in the session variables of the CISCO API and IVR can then able to access that data. I am very good at this.
Currently, my manager plans to move from CISCO IVR to Amazon Connect. Amazon Connect has all infrastructure and IVR can be set up in 45 minutes.
My task is to access existing legacy SOAP web services(which has access to our databases) in AWS Lambda and give that data to IVR.
I went through all the documentation, but not able to figure out where to start. Could some one give me guidance on where to start.
Here's an article about calling SOAP services from a Lambda function, with a walkthrough of the process: https://blog.codecentric.de/en/2016/12/serverless-soap-legacy-api-integration-java-aws-lambda-aws-api-gateway/
It goes further than what you may need, adding API gateway on top of the Lambda function. You may not need that if you're just planning to call those Lambda functions from Connect.
There's also an article in Connect documentation on integrating with Lambda: http://docs.aws.amazon.com/connect/latest/adminguide/connect-lambda-functions.html
My mobile app needs to make secure API calls to on-premise backend services which is not exposed to internet but accessed only by mobile client. How can we secure the backend calls via AWS cloud?
Thanks in Advance
AWS does not have an out-of-the-box solution for what you are looking for. Amazon Cognito's Identity component was designed to secure access to AWS API's, not a developer's. You will have to build your authentication and authorization service for your mobile clients.
Another AWS technology that you may want to consider in your design is Amazon Virtual Private Cloud (VPC), which would allow you to bridge your on-premise network into the AWS cloud. From their you would have to properly secure systems and APIs.
Update 2015-07-09 AWS has announced Amazon API Gateway. Using API Gateway you can build a REST interface to your existing API (or to AWS Lamdba functions) secured with credentials retrieved via an Amazon Cognito authflow. See this blog post for additional announcement details.