Whmcs = 7.3
admin is logged in in the backend,in registration page :
show domain list and price:
When it's ok
but if no admin is logged in in the backend, show no domain list..
Not Ok!
i dump the array of pricing in the template file i got the error :
"An admin user is required to invoke Internal API Commands"
How to show the list even the admin is not logged in ??
Related
when I trying to fetch all product list with rest api.
http://magento-11498-25844-78339.cloudwaysapps.com/api/rest/products
it shows 500 internal server error
As i can see Magento rest API is not configured. Below two steps are required.
Preparing for REST API
These steps are required for utilizing REST API resources:
1. Set up permissions for REST resource operations from Magento Admin Panel.
2. Configure the attributes for different users types in Magento Admin Panel. There are 3 different types of users in accessing the data: Admin, Customer, and Guest. Admin is the backend logged in user, Customer is the fronted logged in user, and Guest is a non-logged in fronted user.
Also you can follow below url for better assistance.
http://devdocs.magento.com/guides/m1x/api/rest/introduction.html
Please follow below Steps which is working fine for me.
1. Login to the admin panel
2. System >> Web services >> Rest Roles
3. Then click on guest then choose catalog all item then save the role
4. Then Click on System >> Web services >> Rest Attributes then Choose all then save.
Hope It will work fine. Thanks
Please look at the screens shots too.
I am trying to create user with Read only permissions for development team to have access to weblogic console , I know the process is simple but for some reason after creating the user i am not able login using the Read only user.
Below steps to create read only user:
Login into Weblogic Admin Console as weblogic user (administrator) ,Then => security realms -> myrealm => users&groups =>New "User" created “appdev” user with password “password01”.
Once user is created, selected username => selected Groups Tab => Selected group by name “Monitors”. Saved the changes made.
Logged out and closed the browser.
Restarted the server and Opened a new browser window.
Attempting to login with the new user is returning access denied.
We are using weblogic 9.2 version.
Check the below link and try to enable refresh replica at startup option and bounce the server and check.
Navigate to weblogic admin console ->Domain->Security->Embedded LDAP->Refresh Replica At StartUp
Detailed descriptions are written below:
http://www.techpaste.com/2013/10/weblogic-admin-server-startup-hanging-coming-running-state/#comment-4532
I'm using FOSUserBundle to manage users in my application.
But finding a problem after login, and after registration.
After registration, a confirmation email is sent successfully, but the redirect page at myapp.com/register/check-email generates the following error:
Impossible to access an attribute ("username") on a NULL variable ("") in FOSUserBundle :: layout.html.twig at line 9
If I click on the link in the email sent to me it seems that the user is successfully activated even if the url myapp.com/register/confirmed returns:
This user does not have access to this section.
If I try to log in, instead of the profiler Symfony signals that are not authenticated in the system.
Apache tomcat version: 6.0.20
If user is already logged, and he tries to login again from login page, the j_security_check is not available error is encountered. Is it normal behaviour or I have to do something?
Actually I have different user roles for accessing different pages, and when access to a page is denied to a particular user, I want to redirect him to login page, where he can login with corresponding credentials.
This behavior is normal: the servlet spec only lays-out the procedure for container-managed authentication (i.e. login) when the user requests a protected resource and the user has not already provided credentials. All other scenarios are left undefined, including yours.
If you want to capture "forbidden" conditions, you can use <error-page> mappings in your WEB-INF/web.xml to send the user anywhere you want, including a login page. Just remember that the container will only accept a login after the above conditions are true, so you may have to log the user out first (by terminating the user's session).
What I might recommend is a "forbidden" page that says "You don't have access to this resource. If you'd like to log-in as a different user to access it, please click [HERE]" where [HERE] is a link to a servlet that terminates the user's session and then redirects to the resource the user was trying to access. This will cause the container to request authentication (i.e. present the login form), verify the credentials, and send the user to the desired resource.
If you are using a container (and webapp) along with version 3.0 of the servlet specification, there is a new HttpServletRequest.login() method that can be used to programmatically log a user into your webapp. You might be able to use that instead of terminating the session and doing all those redirects... instead, you could collect the username and password yourself and then ask the container to do the login for you.
I'm running Joomla! 1.5.22 on localhost.
For the website's registration, after the user fills in all the information and click on 'send registration', the page simply 'refresh' only.
So i tried to log in with the new user's username and password but it only 'refresh' the page and the user isn't logged in.
May i know what is the problem?
Sorry as i'm a beginner in Joomla!
as you said that you are trying to create a user on your local host first check the followings by default settings in your joomla administrator pannel cause as i see in joomla 1.5.22 version if you will create a user then you should have to verify that user, in by default settings >> you will found the settings at :
login at admin pannel
click on site menu and choose > global configuration.
click on the system tab
then you will found the user settings: set No in the new user account activation and then register and try to login,,
IMP: if you will try this setting on real server then suggest you set Yes option on the new user account activation..