finally got the v0.110 to work, so will probably stick with that for a little bit
I'd definitely like to get it working on the newer code, just don't have time to dig through the code to find the missing bits/bobs. If you've got a working sample config I don't mind giving it another go
the configuration on mojito.global: https://www.mojito.global//docs/guides/install/ are the ones that should work well with the master branch
on master
I've updated the doc with proper settings for the release binaries on: https://www.mojito.global//docs/. Added extra entries for springboot2/master branch. @marksteele thanks for bearing with the project!
spring.flyway.clean-disabled=true
l10n.flyway.clean=false
spring.datasource.url=jdbc:mysql://${MOJITO_DB_HOST}:${MOJITO_DB_PORT}/${MOJITO_DB_NAME}?characterEncoding=UTF-8&useUnicode=true&useSSL=false
spring.datasource.username=${MOJITO_DB_USERNAME}
spring.datasource.password=${MOJITO_DB_PASSWORD}
spring.datasource.driverClassName=com.mysql.cj.jdbc.Driver
l10n.org.quartz.jobStore.useProperties=true
l10n.org.quartz.scheduler.instanceId=AUTO
l10n.org.quartz.jobStore.isClustered=true
l10n.org.quartz.threadPool.threadCount=10
l10n.org.quartz.jobStore.class=org.quartz.impl.jdbcjobstore.JobStoreTX
l10n.org.quartz.jobStore.driverDelegateClass=org.quartz.impl.jdbcjobstore.StdJDBCDelegate
l10n.org.quartz.jobStore.dataSource=myDS
l10n.org.quartz.dataSource.myDS.provider=hikaricp
l10n.org.quartz.dataSource.myDS.driver=com.mysql.jdbc.Driver
l10n.org.quartz.dataSource.myDS.URL=jdbc:mysql://${MOJITO_DB_HOST}:${MOJITO_DB_PORT}/${MOJITO_DB_NAME}?characterEncoding=UTF-8&useUnicode=true&useSSL=false
l10n.org.quartz.dataSource.myDS.user=${MOJITO_DB_USERNAME}
l10n.org.quartz.dataSource.myDS.password=${MOJITO_DB_PASSWORD}
l10n.org.quartz.dataSource.myDS.maxConnections=12
l10n.org.quartz.dataSource.myDS.validationQuery=select 1
## OAUTH2
l10n.security.authenticationType=DATABASE,OAUTH2,HEADER
l10n.security.unauth-redirect-to=/login/oauth2/authorization/google
spring.security.oauth2.client.registration.google.client-id=${MOJITO_GOOGLE_CLIENT_ID}
spring.security.oauth2.client.registration.google.client-secret=${MOJITO_GOOGLE_CLIENT_SECRET}
spring.security.oauth2.client.registration.google.authorization-grant-type=authorization_code
spring.security.oauth2.client.registration.google.scope=profile
info.build.version=0.111-SNAPSHOT
spring.mail.host=localhost
spring.session.store-type=none
spring.mustache.suffix:.html
server.tomcat.relaxed-query-chars=[,]
spring.jpa.open-in-view=false
management.health.ldap.enabled=false
management.endpoint.shutdown.enabled=true
management.metrics.export.statsd.enabled=false
org.springframework.http.converter.json.indent_output=false
spring.jpa.hibernate.use-new-id-generator-mappings=false
is the final config I ended up with
works with oauth2 and google
only thing I have yet to figure out is why my cli can talk to the API even though I didn't do any setup for authenticating it
9 replies
@Component
public class SystemPromptCredentialProvider implements CredentialProvider {
@Value("${user.name}")
String systemUserName;
@Value("${user.password}")
String password;
@Override
public String getUsername() {
return systemUserName;
}
@Override
public String getPassword() {
if (password == null) {
System.out.println("Enter password for mojito user " + systemUserName + ": ");
char[] readPassword = System.console().readPassword();
password = new String(readPassword);
}
return password;
}
}
essentially just adding the annotation, allows to do -Duser.name=foo -Duser.password=bar
when used in conjunction with -Dl10n.resttemplate.authentication.credentialProvider=CONSOLE
for that use case the normal provider can be used directly. The SystemPrompt was really if you want to read from the console, else it is not really needed. https://www.mojito.global//docs/refs/configurations/#cli-configuration
so
-Dl10n.resttemplate.authentication.username=... -Dl10n.resttemplate.authentication.password=... would work already. No need to change the provider, default one would be fine
We were trying hands-on with product and got stuck when we were using the same repo for our Android and iOS projects it is giving error based on the repo was created and imported from the platform
Eg: if repo is created with iOS strings file and if we pull in Android project then it gives the error
Asset with path [res/values/strings.xml] was not found in repo [Repo Name]
