I have been able to successfully download, compile, and run Shopizer. Unfortunately, when I attempt to display the home page, I get a blank page. By "blank" I mean that there is nothing on the page, not even undisplayable HTML!
I also attempt to log in as the admin. When I point my browser to the admin page (http://localhost:800/admin) I get the login page but when I enter the username and password (admin and password) the Shopizer throws an exception.
I am running this application in Eclipse, so was able to debug the code. I am finding that the exception from the admin login is caused by a failure of the application to read the username from the database. It attempts to get information from the database when you log in, but the query for information on the admin user returns null and that causes an exception to be thrown.
Apparently, it is getting nothing from the database. I am running this using the default H2 database configuration, and from what I have understood reading some of the information on their forum, the H2 database is run as an embedded database in this application. I also understand that on first running the database is initialized and test data is put in. I have also looked at the database file, it has data in it.
Yet for some reason, Shopizer fails to get user info about the admin user. I suspect that some of the other blank pages I am getting are caused at least partially by a failure to read product and other information, as well.
Does anyone know what is causing this failure to read the database? Has anyone else seen this behavior before? Is there something that needs to be done to enable access (Shopizer's documentation is somewhat incomplete so who knows what else might need to be done to make it work)? Or is there something that needs to be done to make it able to read the database?
Are you able to run the app from the command line first
cd shopizer
./mvnw clean install
./mvnw spring-boot:run
When running from eclipse once you have imported shopizer root project make sure the H2 file resides under sm-shop
Have you tried to configure mysql ?
Yes the schema is created and updated during startup
Related
This is in regards to the sample: msal-web-sample-0.1.0
I am using tomcat 9 and maven to build and run the msal-web-sample code. It is building fine and running, loading spring, etc. I am able to go out and get a username and passowrd login. However, when it tries to return back to my system (https://localhost:8443/msal4jsample/secure/aad) it just has a bit "ERROR PAGE!" heading with Home Page link going back to the main tomcat page.
In the tomcat runtime it has:
2021-06-29 15:28:06.108 ERROR 6360 --- [io-8443-exec-10] o.s.b.w.servlet.support.ErrorPageFilter : Cannot forward to error page for request [/secure/aad] as the response has already been committed. As a result, the response may have the wrong status code. If your application is running on WebSphere Application Server you may be able to resolve this problem by setting com.ibm.ws.webcontainer.invokeFlushAfterService to false
Of course, that doesn't apply to my setup.
I see the get in the logs returning back OK and don't see any errors on startup. I am at a loss as to where to go from here. Any thoughts?
Also, is there a non-spring implementation that can be used with java but still using MSAL?
Thanks
Alan
Please share additional information about the error. Do you have trouble regrading AAD? Check your environmental settings (Tomcat) if this isn't the case.
I have developed a Website on a dev environment, using Laravel and Socialite.
Months ago, I set up a project on Facebook Login in order to use it on my website. Login works fine on this environment, no errors.
Now I deployed it to a production environment, and set up a new FB Login for it. But now I got a generic error in the first login attempt.Image below.
Messages are in portuguese. In english: "An error occurred. Close and open your browser again".
If I try again, I get no errors, and Login works.
I have tried with 3-4 test users provided by Facebook, and with all of them the same occur: that error on first attempt, but works fine on a second attempt.
Use the same process on dev (create test user, try to login) and everything works fine. Login with no errors on first attempt.
The first project, for dev, was using API version 2.1. Update to 3.3 and everything continued to works fine.
The second project, for production, already started with API 3.3, and got all the errors described above.
As I copied all files dev->prod, every version (Laravel, Socialite... ) are the same on both environment. Just update hosts, users , database name (...)
Have now idea how to troubleshoot it.
Any help will be appreciate.
I have looked up various answers on here and none has helped me thus far.
I am rebuilding a database project and it is complaining about one particular script:
CREATE USER [doro] FOR LOGIN [doro];
Now there are other scripts under the security folder which are exactly the same with different logins - which it does not complain about.
With this particular user the error is:
SQL71501: User [doro] has an unresolved reference to Login [doro].
I tried following some suggestions and using the "Add New" option to add the login but this made several other errors appear in relation to that login.
I have the master database reference.
Any suggestions appreciated.
Also, does a rebuild sync the dacpac with the original source database or do you have to manually do a compare and update?
thanks,
KS
I have an issue with FileNet-p8:
All simply, I do not have access to a WorkFlow already designed. I have always a popup asking me to authenticate , I use the same Login/psw to access to the Workplace. But always I get the same message :
Unable to get the configuration file WcmApiConfig.properties
I'm workin with the IBM JVM 1.6 and the Firefox browser.
Thanks.
In our environment, you must use IE in order to avoid that error message. We have not been able to get FireFox to work with WorkplaceXT or PCC.
Even when launching PCC from ACCPE we need to use IE.
If you see the login screen, don't even bother with your credentials. It simply will not work.
I have a console application which hosts two WebApi applications using OWIN Self Host approach. One of the apps uses EF6 with Code First. When I run the executable from the bin folder and make a request to the WebApi, everything works like it should - if the database is already created it just returns the results, otherwise it creates the db first. But if I start the console app from Visual Studio (with debugging), I receive the following error:
Additional information: Cannot open database "{db name}" requested by the login. The login failed.
Login failed for user 'sa'.
Anyone has any ideas why this happens?
EDIT: Problem is not related to the self hosted apps. I referenced the dbcontext directly in the console app and the same issue happens. I also tried Integrated Security and it still fails with "Login failed for user '{DOMAIN\USERNAME}'."
EDIT 2: I fixed my problem by doing deleting the .suo file. That helped me find these two questions mentioning the same solution:
Login failed for user "xxx" Failed to open the explicitly specified database solution
EF 4.1 code first causes weird (login) runtime errors
Can anyone say the reason why the .suo file causes this?