[jboss-jira] [JBoss JIRA] (AS7-1338) Remote JNDI support for AS7

[Alexey S. (JIRA)]

    [ https://issues.jboss.org/browse/AS7-1338?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677451#comment-12677451 ] 

Alexey S. commented on AS7-1338:
--------------------------------

Hello.
I have the experience of 11 years  with JBOSS.
Recently we wanna to migrate from JBOSS 6 to JBOSS 7.1.0 final

Here is a part of my code

final Hashtable jndiProperties = new Hashtable();
		 jndiProperties.put(Context.PROVIDER_URL, "remote://localhost:4447");
			jndiProperties.put(Context.INITIAL_CONTEXT_FACTORY, "org.jboss.naming.remote.client.InitialContextFactory");
			jndiProperties.put("remote.connection.default.username","usera");
			jndiProperties.put("remote.connection.default.password","passa");
		Context context;
			try {
				context = new InitialContext(jndiProperties);
		
I may put username and password, I may not put it - all the time I got

ERROR: JBREM000200: Remote connection failed: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed
javax.naming.NamingException: Failed to create remoting connection [Root exception is java.lang.RuntimeException: javax.security.sasl.SaslException: Authentication failed: all available authentication mechanisms failed]
	at org.jboss.naming.remote.client.ClientUtil.namingException(ClientUtil.java:36)
	at org.jboss.naming.remote.client.InitialContextFactory.getInitialContext(InitialContextFactory.java:117)
	at javax.naming.spi.NamingManager.getInitialContext(NamingManager.java:684)
	at javax.naming.InitialContext.getDefaultInitCtx(InitialContext.java:307)
	at javax.naming.InitialContext.init(InitialContext.java:242)
	at javax.naming.InitialContext.<init>(InitialContext.java:216)

JBoss is of course running and the user added to application users.
Any help? Is JBoss 7.1.0 robust enough to port the system from Jboss 6 to it?
                
> Remote JNDI support for AS7
> ---------------------------
>
>                 Key: AS7-1338
>                 URL: https://issues.jboss.org/browse/AS7-1338
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Naming
>            Reporter: Richard Opalka
>            Assignee: John Bailey
>            Priority: Critical
>              Labels: eap6_prd_req
>             Fix For: 7.1.0.Final
>
>
> Add support for remote JNDI after all.  It was agreed that:
> * Remote JNDI would run over Remoting
> * Remote JNDI for EJB is strictly a legacy access protocol, deprecated in favor of "ejb:"
> * The Remote JNDI service would proxy to a specific Context of the server JNDI tree - maybe "java:jboss/shared", maybe something else
> * Server-side services would opt-in to Remote JNDI; initially we'd only support:
> ** Remote EJB interfaces
> ** HornetQ connection factories
> * In the future we may support:
> ** User bindings, so long as they're serializable
> * In the future we will never support:
> ** Proxied DataSources
> ** Proxied JMS invocations
> Initial project tree is at https://github.com/dmlloyd/jboss-remote-jndi for now.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira