[OPENAM-11034] OpenAM 14.0.0 (AM5) ssoadm create-realm error Created: 13/Apr/17  Updated: 21/Sep/17  Resolved: 03/May/17

Status: Resolved
Project: OpenAM
Component/s: ssoadm
Affects Version/s: 14.0.0
Fix Version/s: 14.1.0

Type: Bug Priority: Major
Reporter: Simon Wickham Assignee: Mark de Reeper
Resolution: Fixed Votes: 1
Labels: EDISON
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Target Version/s:
Sprint: AM Sustaining Sprint 37, AM Sustaining Sprint 38
Story Points: 2
Support Ticket IDs:
QA Assignee: Filip Kubáň [X] (Inactive)
Verified Version/s:

 Description   

When creating a new realm with ssoadm in OpenAM 14.0.0 (AM5) reported exception error.

Commands:

./ssoadm create-realm --realm /Example -u amadmin -f <password file location for amAdmin>  -v
./ssoadm create-realm -e /Example -u amadmin -f <password file location for amAdmin>  -v

Output:

Process Request ...
Constructing Request Context...
Validating mandatory options...
Processing Sub Command ...

Executing class, com.sun.identity.cli.realm.CreateRealm.
Authenticating...
Authenticated.
Exception in thread "main" com.google.inject.ConfigurationException: Guice configuration errors:

1) No implementation for org.forgerock.openam.notifications.NotificationBroker annotated with interface org.forgerock.openam.notifications.LocalOnly was bound.
  while locating org.forgerock.openam.notifications.NotificationBroker annotated with interface org.forgerock.openam.notifications.LocalOnly

1 error
    at com.google.inject.internal.InjectorImpl.getProvider(InjectorImpl.java:1004)
    at com.google.inject.internal.InjectorImpl.getInstance(InjectorImpl.java:1009)
    at org.forgerock.guice.core.InjectorHolder.getInstance(InjectorHolder.java:85)
    at com.sun.identity.idm.plugins.internal.AgentsRepo.<init>(AgentsRepo.java:183)
    at com.sun.identity.sm.OrganizationConfigManager.createSubOrganization(OrganizationConfigManager.java:344)
    at com.sun.identity.cli.realm.CreateRealm.handleRequest(CreateRealm.java:86)
    at com.sun.identity.cli.SubCommand.execute(SubCommand.java:296)
    at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:217)
    at com.sun.identity.cli.CLIRequest.process(CLIRequest.java:139)
    at com.sun.identity.cli.CommandManager.serviceRequestQueue(CommandManager.java:581)
    at com.sun.identity.cli.CommandManager.<init>(CommandManager.java:178)
    at com.sun.identity.cli.CommandManager.main(CommandManager.java:155)
u9503020@forgerock:/opt/forgerock/openam1/tools/admin/AM-5.0.0/bin$


 Comments   
Comment by Mark de Reeper [ 01/May/17 ]

A workaround for this issue is to make use of the new Amster configuration utilities (which are replacing ssoadm in future OpenAM releases) - https://backstage.forgerock.com/docs/amster/5/entity-reference/chapter-amster-entity-reference#sec-amster-entity-realms

Comment by Filip Kubáň [X] (Inactive) [ 31/May/17 ]

Verified on OpenAM 14.1.0-RC3 Build 762bd23f83 (2017-May-11 07:52)

./ssoadm create-realm -e /Example -u amadmin -f pwd.txt

Realm was created.
Generated at Tue Sep 22 11:19:58 UTC 2020 using Jira 7.13.12#713012-sha1:6e07c38070d5191bbf7353952ed38f111754533a.