I am using google oauth client and spring boot in one of my projects. Our team want to upgrade spring boot to 3. Since our project is using google oauth client and google big query client, I am looking for Jakarta EE 9 supported release for google oauth client. My understanding is that google oauth client 1.34.1 does not support Jakarta EE 9 and therefore this dependency will be a blocker for our upgrade. Any idea if an alternate is available to avoid this block?
Thanks in advance.
Searched on maven repository and 1.34.1 is the latest release for google oauth client library.
Related
Liferay Push Notification use Google Cloud Messaging, but recently Google replaced GCM with firebase cloud messaging. Could you please tell me if your push plugin supports FCM or if there is any solution on how to make it work with FCM?
GCM still works, the service hasnt been stop.
Although Liferay doesnt support FCM, i dont doubt it will.
https://firebase.google.com/support/faq/
For Liferay 6.2 EE, Liferay Push plugin supports FCM (the EE version of the plugin https://web.liferay.com/marketplace/-/mp/application/48438926) starting with version 1.3.2. For Liferay 7.0+ (both CE and EE) Liferay Push plugin supports FCM starting from version 2.2.0 (https://issues.liferay.com/browse/LPS-70692).
I have an AzureAD registered Web API working correctly. I am able to acquire the access token by means of AcquireTokenAsync. No problems there. However, no I need to downgrade my rest client library to .net 3.5. I am not being able to use ADAL in .net 3.5. AcquireTokenAsync returns a Task, which is not supported in 3.5. I have read in some tutorials that there is a non async verstion of the method (AcquireToken) here. But I just can't access that method. Also, when I try to install that specific version of ADAL(2.19.208020213) I get a Nuget error saying there is no version supported to .Net 3.5
What am I doing wrong?
UPDATE
I am trying to find out which version of ADAL targets .Net 3.5 so I can install it in my project.
UPDATE 2
If ADAL is not supported in .Net 3.5, what are my options to obtain authorization token from Azure AD in .net 3.5?
The library only supports 4.5 because async support was added in that .net release. You may need to dig back to very old versions of the library to get older .net sdk to work. But you would lose significant big fixes and features.
I'm trying to use Atmosphere Framework based Primefaces Push (with WebSockets) on WebSphere Portal 7 (running on WAS 7, which uses Java EE 5 -> Servlet 2.5). I just read that WAS 7 doesn't support WebSockets (doesn't have a WebSockets API), so I'm looking for some kind of workaround.
Is there anyone who had a similar problem and found a solution?
Websockets need at least java ee 7 container and servlet 3.1 API level. If you can switch to longpooling in your component you have a chance, otherwise not. It's not a matter of hack, your server needs to support protocol upgrade.
Since the introduction of of the Facebook Audience Network SDK for iOS, Facebook started to release updates to the two SDKs together. I was wondering... can we use different versions of the SDKs in the same app or there are dependencies that require both to be included and from the same version?
The reason of the question is that they recently dropped support for iOS 5 in the main Facebook SDK while such thing didn't happen on the Audience Network SDK. Therefore I'd like to integrate a pre-drop version of the Facebook SDK together with the latest Audience Network SDK.
Is this possible?
I went through the documentation but I haven't seen anything mentioning this scenario...
The answer is "YES", it can be done. The two SDKs are independent from each other...
I am migrating a JSF application from WebSphere(WAS) 6.1 to WAS 7.0 and I am experiencing html deprecation issues now that I am using the JSP 2.1 API provided with WAS 7.0 as opposed to the JSP 2.0 API provided with WAS 6.1. Weblogic provides the ability to enable backward compatibility (http://docs.oracle.com/cd/E21764_01/web.1111/e13754/compat.htm#i1111538) in the weblogic app deployment descriptor. Is there a similar solution available in WAS 7.0? Is there a way to enable backwards compatibility in a deployment descriptor so the application can use JSF 2.0 API and not face the deprecated html issues?
There is nothing conclusive about this in the WebSphere Application Server 7.0 documentation, therefore I am led to believe that the typical IBM strategy is used here: The JSP engine you're getting with WAS 7.0 is JSP 2.1 compatible, period. You can't replace it and can't instruct WAS to use an older specification level.