In Magento how to keep store offline or maintenance mode from admin side.
Admin must able to surf the magento store, but restricted to other users.
Any plugin or script or how to do it from admin login.
http://www.magentocommerce.com/magento-connect/store-maintenance.html
provides exactly what you are looking for and more
Check out this http://www.magentocommerce.com/magento-connect/all4coding-offline-maintenance-page.html it provide exactly what you are looking for. compatible with magento 1.4 - 1.8
Related
I am working on HCL commerce 9.1 ,We are able to enable the Page composer for arrora store (Default),But we are not able to enable the Page composer for emerald store,How to enable the Page composer for emerald store.Any help will be appriciated.
You didn't give enough detail to answer your question. You are confusing composers, there are two, commerce composer which is used with the aurora store. Then there is the page composer for react based stores. This was released in 9.1.7, you didn't specify which version you are using. To make page composer work in the development environment, you need to download the react server and install and configure it in the toolkit. Here is a link to the instructions:
https://help.hcltechsw.com/commerce/9.1.0/install/tasks/t91storesdk.html
My organization has decided to use Drools as a decision management framework. We are using the new UI business-central which is deployed as a WAR file in WildFly server for managing the rules and the assets related to the rules.
We have licensed Gsuite for our emails and other activities. We want to use Google login for the users of the business-central system instead of the username and password-based auth provided.
One way to do it is by using a Keycloak server which will provide us a way to manage users and authentication. But we do not want to maintain an extra server just for authentication.
Can someone please help me in achieving this authentication? Also, it would be helpful if I can know in advance the pitfalls of such a type of authentication approach.
Here are the version details for the drools system:
Java: openjdk version "1.8.0_242"
Drools: 7.33.0.Final
After doing a lot of trial and error and quite a bit of googling around. I have reached the conclusion that providing social login in business-central should be done via Keycloak if you are using Wildfly.
There are a lot of security-related features that you will get out of the box and you won't have to tweak around the drools code and later on finding out that you have missed a use case.
I followed official documentation from : https://docs.wso2.com/display/IS541/Integrating+WSO2+Identity+Server+with+Liferay to Login in my Liferay Portal with wso2is user, but it not work for me in wso2is-5.4.1 and liferay6.2ga6. When I try login, liferay's log print "Primary URL :https://wso2is.local:9443/services/Secondary URL :null" but no call to wso2is server is done.
I added this lines into my portal-ext.properties :
auth.pipeline.pre=org.wso2.liferay.is.authenticator.WSO2ISAuthenticator auth.pipeline.enable.liferay.check=false wso2is.auth.service.endpoint.primary=https://wso2is.local:9443/services/ wso2is.auth.thrift.endpoint=localhost wso2is.auth.thrift.port=10500 wso2is.auth.thrift.connection.timeout=10000 wso2is.auth.thrift.admin.user=admin wso2is.auth.thrift.admin.user.password=admin wso2is.auth.thrift.endpoint.login=https://wso2is.local:9443/ wso2is.auth.thrift.system.trusstore=/wso2is-5.4.1/repository/resources/security/wso2carbon.jks wso2is.auth.thrift.system.trusstore.password=wso2carbon
Is there something wrong?
Unfortunately, a lot of the WSO2 documentation is very crufty, containing articles that have been pulled forward from previous versions of the documentation without regression testing on the use cases they present. In short, there's stuff in the documentation that plain doesn't work. If you look at the bottom of the article you'll see the following:
Please note that the above configuration is tested with Liferay 6.1.1
and WSO2 Identity 3.2.3/4.0.0.
I recall I tested this a long time ago, and determined that it wouldn't work with the current version, but that was so long ago that I can't remember why. In any case, the approach presented for integrating Liferay was offered at a time where Liferay didn't have the ability to use standardized authentication protocols like SAML. Now that it does, you probably want to do it in a standards compliant manner instead of using an authentication interface Liferay only promotes using for proprietary authentication systems.
My suggestion is that if you are using Liferay portal enterprise with LDAP that you use the built-in SAML connector. If you aren't using Enterprise, there are some compatible authenticator extensions in the extensions store that will also integrate with Liferay. If you configure Liferay to be a client against WSO2 and then integrate Liferay to LDAP on the backend, it also allows Liferay to be used as a user dashboard instead of the jaggery based one that comes in the product.
is there a possibility in TYPO3 LTS 8 to make the backendmodul "Indexing" accessible for non admin users? I miss this module in the access lists in backend user group configuration.
Thanks!
That is not possible out of the box. As a solution I would propose to override the configuration with a 3rd party extension or applying diff files during composer install (see https://github.com/cweagans/composer-patches).
In http://en.wikipedia.org/wiki/Comparison_of_issue-tracking_systems#Input_interfaces it says, that Mantis allows Input via mail.
I checked config_defaults_inc.php for associated settings, but could not find them. How can I allow my users to send issues to my MantisBT instance?
You will have to install the EmailReporting plugin to enable this feature. You can download the plugin from https://github.com/mantisbt-plugins/EmailReporting
Installation of the plugin is straightforward, but configuration can be done only from the plugin page. Please make sure that you read the README before using the plugin.
If you are using MantisHub (MantisBT as a Service), email reporting is included as part of the gold and platinum plans:
http://www.mantishub.com/
You can find the documentation of the feature at:
http://support.mantishub.com/hc/en-us/articles/204273585-Using-Email-Reporting