Hipster stack for Java developers. Spring Boot + Angular in one handy generator.
I have created a java monolithic project through jhipster and I tried to sign in but getting error.
Compiled successfully.
<e> [webpack-dev-server] [HPM] Error occurred while proxying request localhost:9000/api/account to http://localhost:8080/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
<e> [webpack-dev-server] [HPM] Error occurred while proxying request localhost:9000/management/info to http://localhost:8080/ [ECONNREFUSED] (https://nodejs.org/api/errors.html#errors_common_system_errors)
Can anyone please help me with this?
I'm preparing an Issue with the jhipster-generator (7.8.0 and possibly earlier) and the Administration API feature tied into OpenAPI. Basically, the UI will load, but the regular expression used for validation of login, e.g., AdminUserDTO.login causes rendering errors.
It appears that this is a known issue as the generator/generator-constants.js defines a LOGIN_REGEX_JS explicitly to circumvent the lack of PCRE support for atomic subgroups in JavaScript RegExp. However, this value is not surfaced to the OpenAPI definitions for the DTOs.
I'm just now getting into the source code, so this may take some time, but there might be some more experienced contributors that could guide me here. I'm literally just forking the project.
Some images for context...
2 replies
Hi! I'm deploying Jhipster Registry with docker-compose but I'm struggling with something really simple. How can I see the app dashboards described in docs (metrics, health, logging...)? I don't see any button and/or menu that let me access to these views :S
For anyone interested... I've found what was "the issue". After some research I think I have found the problem.
Apparently the documentation is outdated because these screens are NOT already in the JHipster Registry code. These views were up to version 7.0.0 when it was removed from the code (example for health page: https://github.com/jhipster/jhipster-registry/compare/v6.8.0...v7.0.0#diff-dc2f7893e7ea938b41bc35f06f9e156e649df5f7bcaf0f8f34c01675d513a3d9)
Does anyone here know why this support was removed? In my case I use JHipster with microservices and I wouldn't want to have to stay on version 6.8.0 just to be able to have these screens...
Hello everyone,
does anyone know how to ignore a field in the relational database but not in elasticsearch?
the details of the question : https://stackoverflow.com/questions/71843478/spring-data-how-to-ignore-field-for-relational-database-but-not-in-elasticsearc
generating application in repository bharathyes/some-demo I checked and no such repo have been created even after many minutes of this running without any progress. What should I be here? I wanted to try the online gen because I was having issues with the cli gen + my JDL doc.
Hi, I am getting an error when i run npm start to load my front end: C:\Users\rahma\git\TaskManager>npm start
task-manager@0.0.1-SNAPSHOT start
ng serve --hmr
NOTICE: Hot Module Replacement (HMR) is enabled for the dev server.
See https://webpack.js.org/guides/hot-module-replacement for information on working with HMR for Webpack.
- Generating browser application bundles (phase: setup)...An unhandled exception occurred: compiler.plugin is not a function
See "C:\Users\rahma\AppData\Local\Temp\ng-5WfuI2\angular-errors.log" for further details. Here is what i see in the angular file: [error] TypeError: compiler.plugin is not a function
at Plugin.apply (C:\Users\ \git\TaskManager\node_modules\browser-sync-webpack-plugin\index.js:14:12)
at createCompiler (C:\Users\ \git\TaskManager\node_modules\webpack\lib\webpack.js:73:12)
at create (C:\Users\ \git\TaskManager\node_modules\webpack\lib\webpack.js:134:16)
at webpack (C:\Users\ \git\TaskManager\node_modules\webpack\lib\webpack.js:158:32)
at Object.f [as webpackFactory] (C:\Users\ \git\TaskManager\node_modules\webpack\lib\index.js:63:16)
at createWebpack (C:\Users\ \git\TaskManager\node_modules\@angular-devkit\build-webpack\src\webpack-dev-server\index.js:24:36)
at runWebpackDevServer (C:\Users\ \git\TaskManager\node_modules\@angular-devkit\build-webpack\src\webpack-dev-server\index.js:43:12)
at SwitchMapSubscriber.project (C:\Users\ \git\TaskManager\node_modules\@angular-devkit\build-angular\src\builders\dev-server\index.js:195:56)
at SwitchMapSubscriber._next (C:\Users\ \git\TaskManager\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\operators\switchMap.js:47:27)
at SwitchMapSubscriber.Subscriber.next (C:\Users\ \git\TaskManager\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\Subscriber.js:66:18)
at C:\Users\ \git\TaskManager\node_modules\@angular-devkit\build-angular\node_modules\rxjs\internal\util\subscribeToPromise.js:7:24
Hey guys, i am new in jHipster world. Anyway trying to set up my local, before i will push everything to repos and share it to other co-workers.
Everything seems working fine, except one thing:
jHipster microservice Swagger-UI is not available in registry / control center API tab
I see my test microservice / api gateway in health check, metrics, instances - but they are not visible in API tab
more details here: https://stackoverflow.com/questions/72010061/jhipster-microservice-swagger-ui-not-available-in-registry-control-center-api
any ideas?
1 reply
UserService gets my Authorities and User Attributes in the OAuth2AuthenticationToken but something goes wrong with the CustomClaimConverter and possibly with SecurityUtils. I'm able to create an ArrayList<String> in the CustomClaimConverter and hand it to the roles and it works. So... pointers as to what I might be missing?2022-04-28 10:23:27.602 DEBUG [MafPoc,,] 93485 --- [ XNIO-1 task-10] c.k.poc.web.rest.AccountResource : Enter: getAccount() with argument[s] = [OAuth2AuthenticationToken [Principal=Name: [_arY4Yo...],
Granted Authorities: [[ROLE_USER, SCOPE_email, SCOPE_openid, SCOPE_profile]],
User Attributes: [{sub=_arY4Yo... aio=AVQAq/8TAA...,
xms_pl=en,
roles=["ROLE_ADMIN","ROLE_USER"],
iss=https://login.microsoftonline.com/88888888-UUID-4444-4444-121212121212/v2.0, oid=88888888-UUID-4444-4444-121212121212,
preferred_username=azuredev@domain.com,
tid=88888888-UUID-4444-4444-121212121212,
sid=88888888-UUID-4444-4444-121212121212,
login_hint=O.CiQw...,
ctry=US,
auth_time=2022-04-28T14:23:26Z,
exp=2022-04-28T15:23:26Z,
ipaddr=333.22.22.333,
iat=2022-04-28T14:18:26Z,
email=azuredev@domain.com,
ver=2.0,
xms_tpl=en,
groups=["88888888-UUID-4444-4444-121212121212","88888888-UUID-4444-4444-121212121212","88888888-UUID-4444-4444-121212121212"],
uti=vK3G...,
given_name=Timothy,
nonce=_YUA9Z...,
picture=https://graph.microsoft.com/v1.0/me/photo/$value,
tenant_ctry=US,
aud=[88888888-UUID-4444-4444-121212121212],
tenant_region_scope=NA,
nbf=Thu Apr 28 10:18:26 EDT 2022,
idp=https://sts.windows.net/88888888-UUID-UUID-4444-121212121212/,
rh=0.AX0AhSp...,
name=Timothy Stone,
family_name=Stone,
acct=0}],
Credentials=[PROTECTED],
Authenticated=true,
Details=WebAuthenticationDetails [RemoteIpAddress=0:0:0:0:0:0:0:1, SessionId=feeE4Fq2k...],
Granted Authorities=[]]]private static Collection<String> getRolesFromClaims(Map<String, Object> claims) {
List<String> roles = new ArrayList<>();
roles.add("ROLE_ADMIN");
return (Collection<String>) claims.getOrDefault(
"groups",
claims.getOrDefault("roles", claims.getOrDefault(CLAIMS_NAMESPACE + "roles", roles))
);
}# claims passed
2022-04-28 14:02:58.055 DEBUG 4846 --- [ XNIO-1 task-1] c.k.poc.security.SecurityUtils : name, Timothy Stone
2022-04-28 14:02:58.055 DEBUG 4846 --- [ XNIO-1 task-1] c.k.poc.security.SecurityUtils : sub, _arY4Yo-...
2022-04-28 14:02:58.055 DEBUG 4846 --- [ XNIO-1 task-1] c.k.poc.security.SecurityUtils : given_name, Timothy
2022-04-28 14:02:58.056 DEBUG 4846 --- [ XNIO-1 task-1] c.k.poc.security.SecurityUtils : family_name, Stone
2022-04-28 14:02:58.056 DEBUG 4846 --- [ XNIO-1 task-1] c.k.poc.security.SecurityUtils : picture, https://graph.microsoft.com/v1.0/me/photo/$value
Should this work? I'm trying to follow the docs with the JDL entities and relating it back to a User
entity Organization {
name String required
}
relationship OneToMany {
Organization{user(login)} to User
}But end up getting an error:
WARNING! Error at 'Organization' definitions: 'otherEntityRelationshipName' is set with value 'organization' at relationship 'user' but no back-reference was found at 'user'
Error running generator entities: Error: Error at entity Organization: could not find the other side of the relationship {
"otherEntityField": "login",
"otherEntityName": "user",
"otherEntityRelationshipName": "organization",
"relationshipName": "user",
"relationshipType": "one-to-many",
"otherEntity": "[User Entity]",
"ownerSide": false,
"collection": true,
"otherSideReferenceExists": false,
"otherEntityIsEmbedded": false
}num_agency. Can I a) edit the resulting JDL or will the generator fail, b) just create and edit without and fixup the resulting entities?
1 reply
.groupBy( { (key: String, word: String) -> word }, Grouped.with(Serdes.String(), Serdes.String()) ) the compiler can't determine which function overload between Grouped<KR!, Any!> and Serialized<KR!, Any!> I'm aiming for the former but I'm not sure how to make this explicit for the compiler. How do I resolve this?
1 reply
3 replies
2 replies
How can I customize or use the jhipster-generator github build? your suggestions are highly appreciated. thanks
2 replies
Hi All, I am trying to use jhipster to generate microservice applications. The back-end code of entity generated by jhipster JDL is in microservice applications, and the front-end code generated is in gateway application .
If in gateway_app \ webpack \environment.js Configure SERVER_API_URL: '' ", then when I operate the generated front-end UI , it calls the URL of the back-end micro service with the address of / API / entities, but the back-end address that needs to be called through the gateway should be / services / app1 / API / entities1
If I set SERVER_API_URL in webpack \environment.js as '' gateway / services / app1 ", then the account address called during OAuth authentication becomes http://gateway/services/app1/api/account , resulting in authentication failure.
How to configure and solve the above problems, thank you for your suggestions.
1 reply
Hi everyone,
Just tried today to limit the permissions I needed to update my application in aws beanstalk, so that I don't have to give:
- AmazonS3FullAccess
- AmazonRDSFullAccess
- IAMFullAccess
I ended up with just AdministratorAccess-AWSElasticBeanstalk plus a policy with the following actions:
- ec2:CreateSecurityGroup
- ec2:DescribeSecurityGroups
- iam:CreateRole
- iam:GetInstanceProfile
- iam:GetRole
- iam:ListRoles
- rds:CreateDBInstance
- rds:DescribeDBInstances
- s3:CreateBucket
- s3:GetObject
- s3:ListBucket
- s3:PutObject
Though I've only tried it with an update, most of the resources (rds, bucket, beanstalk environment) were already created.
Sharing here in case it's useful to anyone..
org.springframework.mail.MailAuthenticationException: Authentication failed; nested exception is javax.mail.AuthenticationFailedException: 535 Authentication Credentials Invalid at org.springframework.mail.javamail.JavaMailSenderImpl.doSend(JavaMailSenderImpl.java:440)
3 replies
Error: error TS100: Can't resolve all parameters for JhiTranslateDirective in node_modules/ng-jhipster/ng-jhipster.d.ts: ([object Object], [object Object], ?).
1 reply