singh_ankit β made their first commit to this issueβs fork.
Working on this as part of DCP2024
Hi @jmee,
I completely understand how frustrating it can be to see that message on the administrative page.
I would like to clarify that this message is not present in the version selected in this issue or in any community variants of the modules that we release here. It might be visible in any licensed variant of the module, which is maintained in a separate directory, and presenting an expiry notification in the licensed module is necessary.
Also, In the latest release of the licensed module, we have updated the message to clearly state which license is expired, how to renew it, and what will happen if it is not renewed. Additionally, this message will only be visible to users with admin role, not to all users. Please upgrade to the latest version.
Hi @robinschlenker,
Thank you for pointing out the issue. I would like to inform you that it has been resolved with version 4.0.8.
Could you please test and confirm the same?
Feel free to reach out to us at drupalsupport@xecurify.com if you have any questions or concerns.
Thank you for letting me know the PHP version and pointing out the issue. This has been fixed in the latest version (2.0.7).
Could you please inform me of the PHP version on which you encountered the issue? According to the PHP manual, a trailing comma is allowed in the list of the function arguments, from PHP 8.0.0.
https://www.php.net/manual/en/functions.arguments.php#:~:text=As%20of%20....
hellow @maseyuk,
I can confirm that both the modules miniorange_oauth_client and oauth_login_oauth2 are maintained by miniOrange. Earlier, the https://www.drupal.org/project/oauth_login_oauth2 β module was primarily intended for providing social login options within Drupal, enabling users to log in using their social media or other identity provider credentials. On the other hand, the https://www.drupal.org/project/miniorange_oauth_client β module is designed to add Single Sign-On functionality to Drupal sites, allowing users to authenticate with a single username and password across interconnected but independent applications.
We apologize for any confusion caused by the similar functionalities of the modules. To streamline the functionality and improve the user experience we have recognized the need to merge both functionalities into a single module. Our team has already started working on this initiative to ensure a seamless integration. In the future, we will be discontinuing one of the modules.
If you have any further questions or concerns regarding the modules, please do not hesitate to contact us at drupalsupport@xecurify.com. We are here to assist you.
This issue has been fixed in the version 4.0.4
Also, please note that the email address, drupalsupport@xecurify.com, does not belong to anyone personally. Instead, it is the designated email address of the maintainers of the module ( https://www.drupal.org/project/oauth_server_sso β ) mentioned in the setup guide. This email address is provided to assist users in configuring the module and addressing any issues they may encounter.
Furthermore, in compliance with your request to avoid using 'mailto' links for support, I want to clarify that the email address is not intended for direct support towards anyone rather to connect users with the relevant module maintainers. If users face any issues they can consider reaching out to the appropriate support channels provided by Drupal or directly to the module maintainers.
Hi @sysosmaster,
With reference to your previous question regarding existing dedicated Drupal OAuth path in Rocket chat-
You are right that Rocket chat have a dedicated Drupal OAuth path, however, it's important to note that the dedicated Drupal path can only be used if someone is using the https://www.drupal.org/project/oauth2_client β module on their Drupal site. (please refer to the documentation - https://docs.rocket.chat/use-rocket.chat/workspace-administration/settings/oauth/other-oauth-setup#drupal-oauth)
This setup guide explains the OAuth integration between Drupal and Rocket chat using the https://www.drupal.org/project/oauth_server_sso β module. This module offers a different approach to integrating Drupal with Rocket chat for OAuth login. If you have any further questions or require further clarification, please feel free to reach out me.