If you are unable to create a new account, please email support@bspsoftware.com

 

News:

MetaManager - Administrative Tools for IBM Cognos
Pricing starting at $2,100
Download Now    Learn More

Main Menu

working with IBM Cognos Framework

Started by Ashwan, 16 Apr 2014 03:48:47 PM

Previous topic - Next topic

Ashwan

When I tried to create a new project they system asked for credentials. I tried to provide my credentials but they system has throw the below error message. Please provide the solution for it, I am very new to this tool. Thanks.
_______________________________________________________________________________________________________________________________________
org.springframework.security.userdetails.UsernameNotFoundException: User humad\axt2411 not foundorg.springframework.security.userdetails.UsernameNotFoundException: User humad\axt2411 not found at com.unica.manager.security.UserManager.createAffiniumUser(UserManager.java:1254) at com.unica.manager.security.UserManager.createAffiniumUser(UserManager.java:1217) at com.unica.manager.security.UserManager$$FastClassByCGLIB$$177f5362.invoke(<generated>) at net.sf.cglib.proxy.MethodProxy.invoke(MethodProxy.java:149) at org.springframework.aop.framework.Cglib2AopProxy$CglibMethodInvocation.invokeJoinpoint(Cglib2AopProxy.java:700) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:149) at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:106) at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:171) at org.springframework.aop.framework.Cglib2AopProxy$DynamicAdvisedInterceptor.intercept(Cglib2AopProxy.java:635) at com.unica.manager.security.UserManager$$EnhancerByCGLIB$$6a5e044c.createAffiniumUser(<generated>) at com.unica.report.adapter.UnicaSecurityUtil.getVisa(UnicaSecurityUtil.java:170) at com.unica.report.adapter.AffiniumAuthenticationProvider.logon(AffiniumAuthenticationProvider.java:80) at com.ibm.cognos.camaaa.internal.customLegacy.auth.NamespaceAuthProviderAdapter.logon(NamespaceAuthProviderAdapter.java:65) at com.ibm.cognos.camaaa.internal.customLegacy.common.handler.CustomJavaProviderHandler.processAuthProviderRequest(CustomJavaProviderHandler.java:206) at com.ibm.cognos.camaaa.internal.customLegacy.common.handler.CustomJavaProviderHandler.handleInboundRequest(CustomJavaProviderHandler.java:167) at com.ibm.cognos.camaaa.internal.common.handler.DefaultHandler.handleMessage(DefaultHandler.java:72) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandler.handleMessage(AuthHandler.java:150) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandlerChain.invokeHandlersForward(AuthHandlerChain.java:78) at com.ibm.cognos.camaaa.internal.common.handler.HandlerChain.handleMessage(HandlerChain.java:211) at com.ibm.cognos.camaaa.internal.common.handler.HandlerBindingImpl.handleRequestRequired(HandlerBindingImpl.java:176) at com.ibm.cognos.camaaa.internal.common.handler.HandlerDispatcher.handleRequestRequired(HandlerDispatcher.java:180) at com.ibm.cognos.camaaa.internal.common.handler.InvokeNamespaceHandler.dispatchRequestToNamespace(InvokeNamespaceHandler.java:81) at com.ibm.cognos.camaaa.internal.common.handler.InvokeNamespaceHandler.handleInboundRequest(InvokeNamespaceHandler.java:154) at com.ibm.cognos.camaaa.internal.common.handler.DefaultHandler.handleMessage(DefaultHandler.java:72) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandler.handleMessage(AuthHandler.java:150) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandlerChain.invokeHandlersForward(AuthHandlerChain.java:78) at com.ibm.cognos.camaaa.internal.common.handler.HandlerChain.handleMessage(HandlerChain.java:211) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandler.handleMessage(AuthHandler.java:150) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandlerChain.invokeHandlersForward(AuthHandlerChain.java:78) at com.ibm.cognos.camaaa.internal.common.handler.HandlerChain.handleMessage(HandlerChain.java:211) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandler.handleMessage(AuthHandler.java:150) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandlerChain.invokeHandlersForward(AuthHandlerChain.java:78) at com.ibm.cognos.camaaa.internal.common.handler.HandlerChain.handleMessage(HandlerChain.java:211) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandler.handleMessage(AuthHandler.java:150) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandlerChain.invokeHandlersForward(AuthHandlerChain.java:78) at com.ibm.cognos.camaaa.internal.common.handler.HandlerChain.handleMessage(HandlerChain.java:211) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandler.handleMessage(AuthHandler.java:150) at com.ibm.cognos.camaaa.internal.auth.handler.AuthHandlerChain.invokeHandlersForward(AuthHandlerChain.java:78) at com.ibm.cognos.camaaa.internal.common.handler.HandlerChain.handleMessage(HandlerChain.java:211) at com.ibm.cognos.camaaa.internal.common.handler.HandlerBindingImpl.handleRequestRequired(HandlerBindingImpl.java:176) at com.ibm.cognos.camaaa.internal.common.handler.HandlerBindingImpl.handleRequest(HandlerBindingImpl.java:158) at com.ibm.cognos.camaaa.internal.common.handler.HandlerDispatcher.handleRequest(HandlerDispatcher.java:165) at com.ibm.cognos.camaaa.internal.common.service.CAMCommonServiceHandler.processRequest(CAMCommonServiceHandler.java:549) at com.ibm.cognos.camaaa.internal.common.service.CAMCommonServiceHandler.invokeImpl(CAMCommonServiceHandler.java:393) at com.ibm.cognos.camaaa.internal.common.service.CAMAsyncServiceHandler.invokeImpl(CAMAsyncServiceHandler.java:97) at com.ibm.cognos.camaaa.internal.bridge.CmBridge.processSoapRequest(CmBridge.java:656) at com.ibm.cognos.camaaa.internal.bridge.CmBridge.Authenticate(CmBridge.java:173) at com.cognos.cm.cam.AAAProvider_CAM.invoke(AAAProvider_CAM.java:38) at com.cognos.cm.cam.AAAProvider_CAM.invoke(AAAProvider_CAM.java:117) at com.cognos.cm.cam.AAACounterProxy.invoke(AAACounterProxy.java:72) at com.cognos.cm.cam.CMAAAProxyBase.invoke(CMAAAProxyBase.java:98) at com.cognos.cm.server.AccMan.invokeCAMAuthenticate(AccMan.java:283) at com.cognos.cm.server.AccMan.Authenticate(AccMan.java:181) at com.cognos.cm.server.RequestManager.AuthenticateCAMHeader(RequestManager.java:3019) at com.cognos.cm.server.RequestManager.handleRequest(RequestManager.java:2501) at com.cognos.cm.server.RequestManager.executeTheRequest(RequestManager.java:1194) at com.cognos.cm.server.RequestManager.handle(RequestManager.java:520) at com.cognos.cm.server.CMServlet.doPost(CMServlet.java:636) at com.cognos.cm.server.ContentManager.doPost(ContentManager.java:131) at javax.servlet.http.HttpServlet.service(HttpServlet.java:637) at com.ibm.cognos.pogo.zipi.ZipiWrappedServlet.service(ZipiWrappedServlet.java:29) at javax.servlet.http.HttpServlet.service(HttpServlet.java:717) at com.cognos.pogo.isolation.ServletWrapper.service(ServletWrapper.java:258) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:290) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:206) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:233) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:191) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:102) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:109) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:293) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:859) at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:602) at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:489) at java.lang.Thread.run(Thread.java:736)

MFGF

Hi,

What a lovely error! :)  The message seems to be telling you "user name not found".

Regards,

MF.
Meep!

Ashwan

I need solution not smilees...and I know that user name not found but the point is what I can do in order to solve this issue ?

Raghuvir

Hi Ashwan,

Chill... Respect MFGF...

You need to provide valid credentials. Check the namespace you have mapped to the cognos and which users are present in it. Once the user is present in the namespace and u have a valid password for the user, u wont have any issues to log in.

Regards

MFGF

Quote from: Ashwan on 17 Apr 2014 08:48:39 AM
I need solution not smilees...

Hmmm. Sounds like a little attitude creeping into your post here? This, my friend, is not the way we do things on Cognoise. I'd politely ask you to remain civil if you intend to continue posting on this forum. As you're new to the forum I'm going to cut you some slack and suggest we start over on a friendly footing. If I or any of the other moderators see you use this kind of bad attitude from here on, though, you will be banned - just so we're clear.

So... The key question is whether the user name you entered is valid or not in the authentication provider you are using. What security provider is being used? The likelihood is that it's one of two issues - either your user name is not there at all, or else the config of your Cognos instance is incorrect and the search for your user name in the provider is pointing to the wrong place. As we don't have access to your system we can't tell you exactly what the solution will be, but hopefully this will point you in the right direction and/or give you some useful questions you can ask of the person responsible for your system. Do you know (for example) if other users have the same issue?

Cheers, and welcome to Cognoise.

MF.
Meep!

Raghuvir

hi Ashwan,

Please read through the Forum Etiquette  :)

This is a very nice place to be, get to learn a lot of things and solutions for your queries. so leats just respect this place and all members here

Regards

Ashwan

Friends, I really did not mean it. I appologise if it has hurt any one. I received the answer in casual manner hence I replied accordingly but dint mean to show any attitude or else being disrespectful to any one. I am working on your suggestions and thanks for them :-)

Ashwan

Hi MFGF,

We just started using this tool and is very new even to the administrator. He installed the softwre and not sure abou the things that you are talking about.
You spoke about :
MFGF: User name is not there in the authentication provider
Where do I need to check for authentication provider?

MFGF: What security provider is being used?
I am not sure about this.

Please let me know the paths wher I can check for these things.
I have got the following steps from IBM site,
1.In the location where you installed Content Manager, start IBM Cognos Configuration.
2.In the Explorer window, under Data Access, Content Manager, click Content Store.
3.In the Properties window, for the Database name property, type the name of the database or the database alias.
4.Change the logon credentials to specify a valid user ID and password:
•Click the Value box next to the User ID and password property and then click the edit button when it appears.
•Type the appropriate values and click OK.

But I do not see the content manager installed in my system, is it required to be installed to work with Framework.
I directly opened the cognos configuration but I do not see content manager (as it is not installed).

Please suggest on this.

Thanks,
Ashwan.





What security provider is being used? The likelihood is that it's one of two issues - either your user name is not there at all, or else the config of your Cognos instance is incorrect and the search for your user name in the provider is pointing to the wrong place. As we don't have access to your system we can't tell you exactly what the solution will be, but hopefully this will point you in the right direction and/or give you some useful questions you can ask of the person responsible for your system. Do you know (for example) if other users have the same issue

MFGF

Hi,

Before you go any further, read Chapter 13 of the Installation and Configuration Guide:

http://public.dhe.ibm.com/software/data/cognos/documentation/docs/en/10.2.1/inst_cr_winux.pdf

It describes authentication (security) providers and how they are added and configured for use with a Cognos instance. Once you have a grasp of this, you can check to see which authentication provider you are using. Once you know this, you can find out from whoever administers this whether you have a valid login defined there.

The steps you mention below are to modify the login being used by Cognos to connect to the content store database it is using. If this was incorrect, Cognos would not be able to connect to it and the service would be unable to start, so this is not your issue.

Somebody somewhere must have installed and configured your Cognos instance. Are they still around? Can you recruit their help? If you don't understand the architecture and admin side, you will find it incredibly difficult to troubeshoot issues like this on your own.

You are seeing this issue from Framework Manager, right? However, Framework Manager is probably installed on your local machine and configured to talk to your cognos server. Authentication (ie logging in) is done on the server not on your local machine, so you need to be looking in the configuration on the server to see which authentication provider you have (and also to see the Content Manager config settings you mentioned).

Cheers!

MF.
Meep!