CRJCA0069E
I get the error below when browsing to the Lifecycle Project Administration screen and in the JTS setup wizard on the LPA section.
The error doesn't seem to happen when I point my data warehouses to Derby, only when they point to Oracle. Also the warehouse jobs run fine on Derby, but fail on the common jobs on Oracle. 2011-07-21 15:12:09,131 ERROR com.ibm.team.lpa.config - An uncaught Exception has been thrown com.ibm.team.jfs.app.http.HttpInternalServerErrorException: CRJCA0069E An unexpected error occurred while building an OAuth authorization response. at com.ibm.team.lpa.common.auth.OAuthUtils.createOAuthAuthorizationException(OAuthUtils.java:82) at com.ibm.team.lpa.common.auth.OAuthInterceptor.process(OAuthInterceptor.java:78) at com.ibm.team.jfs.app.http.internal.context.ServiceContextBean.process(ServiceContextBean.java:61) at com.ibm.team.jfs.app.http.internal.context.ServiceContextBean.process(ServiceContextBean.java:66) at com.ibm.team.lpa.common.services.AbstractLpaRestHandler.dispatch(AbstractLpaRestHandler.java:296) at com.ibm.team.lpa.common.services.AbstractLpaRestHandler.handle(AbstractLpaRestHandler.java:324) at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:299) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:420) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:811) Caused by: com.ibm.team.jfs.app.oauth.OAuthInvalidConsumerKeyException: CRJZS0033E The consumer key is not valid and the consumer may not be registered. The service provider is "https://dswwindap09.div16.ibm.com:9443". The consumer key is "4c3...247". at com.ibm.team.jfs.app.oauth.OAuthHelper.checkResponseForOAuthErrorsInternal(OAuthHelper.java:1293) at com.ibm.team.jfs.app.oauth.OAuthHelper.getToken(OAuthHelper.java:1418) at com.ibm.team.jfs.app.oauth.OAuthHelper.getNewRequestTokenFromProvider(OAuthHelper.java:845) at com.ibm.team.lpa.common.auth.OAuthUtils.createOAuthAuthorizationException(OAuthUtils.java:78) ... 29 more |
19 answers
|
Admin Log
2011-08-03 06:26:13,788 WARN com.ibm.team.lpa.http - CRJCA0042W Host https://dswwindap09.div16.ibm.com:9443 has indicated a problem with an LPA request. >>> GET https://dswwindap09.div16.ibm.com:9443/jts/proxy?uri=https%3A%2F%2Fdswwindap09.div16.ibm.com%3A9443%2Frm%2FprocessProxy%3Furi%3Dhttps%253A%252F%252Fdswwindap09.div16.ibm.com%253A9443%252Fjts%252Fprocess%252Fproject-areas HTTP/1.1 >>> X-Requested-With: JazzHttpClient >>> X-socket-timeout: 600 <<< HTTP/1.1 500 Internal Server Error <<< Server: Apache-Coyote/1.1 <<< Content-Type: text/html;charset=utf-8 <<< Content-Length: 3709 <<< Date: Wed, 03 Aug 2011 10:26:13 GMT <<< Connection: close <html><head><title>Apache Tomcat/5.5.30 - Error report</title><style><H1></style> </head><body><h1>HTTP Status 500 - </h1><HR><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error () that prevented it from fulfilling this request.</u></p><p><b>exception</b> <pre>com.ibm.team.jfs.app.oauth.OAuthInvalidSignatureException: CRJZS0035E The OAuth signature is not valid. com.ibm.team.jfs.app.oauth.OAuthHelper.checkResponseForOAuthErrorsInternal(OAuthHelper.java:1296) com.ibm.team.jfs.app.oauth.OAuthHelper.getToken(OAuthHelper.java:1418) com.ibm.team.jfs.app.oauth.OAuthHelper.getNewRequestTokenFromProvider(OAuthHelper.java:845) com.ibm.team.repository.service.internal.auth.proxy.AuthProxy.createNewAppCreds(AuthProxy.java:893) sun.reflect.GeneratedMethodAccessor1405.invoke(Unknown Source) sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) java.lang.reflect.Method.invoke(Method.java:618) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.invoke(ExportProxyServiceRecord.java:370) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord.access$0(ExportProxyServiceRecord.java:356) org.eclipse.soda.sat.core.internal.record.ExportProxyServiceRecord$ExportedServiceInvocationHandler.invoke(ExportProxyServiceRecord.java:56) $Proxy339.createNewAppCreds(Unknown Source) com.ibm.team.repository.service.internal.auth.proxy.OAuthAccessTokenStorageServiceImpl.requestAuthenticationURL(OAuthAccessTokenStorageServiceImpl.java:61) net.jazz.ajax.service.auth.OAuthProvider.authenticationURL(OAuthProvider.java:80) net.jazz.ajax.service.internal.http.ProxyOperation$1.handleResponse(ProxyOperation.java:141) com.ibm.team.jfs.app.http.client.JazzHttpClient.execute(JazzHttpClient.java:257) org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:717) net.jazz.ajax.service.auth.AuthenticatingClientService.execute(AuthenticatingClientService.java:119) net.jazz.ajax.service.internal.http.ProxyOperation.run(ProxyOperation.java:130) net.jazz.ajax.service.internal.http.ProxyServlet.service(ProxyServlet.java:57) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) net.jazz.ajax.servlets.LoggingHttpServlet.service(LoggingHttpServlet.java:34) org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:59) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) com.ibm.team.repository.server.servletbridge.JazzServlet.service(JazzServlet.java:76) javax.servlet.http.HttpServlet.service(HttpServlet.java:729) </pre></p><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/5.5.30 logs.</u></p><HR><h3>Apache Tomcat/5.5.30</h3></body></html> 2011-08-03 06:26:16,491 WARN com.ibm.team.lpa.http - CRJCA0042W Host https://dswwindap09.div16.ibm.com:9443 has indicated a problem with an LPA request. >>> GET https://dswwindap09.div16.ibm.com:9443/jts/jauth-proxy?url=https%3A%2F%2Fdswwindap09.div16.ibm.com%3A9443%2Frm%2FprocessProxy%3Furi%3Dhttps%253A%252F%252Fdswwindap09.div16.ibm.com%253A9443%252Fjts%252Fprocess%252Fproject-areas HTTP/1.1 >>> Accept: application/xml <<< HTTP/1.1 500 <<< Server: Apache-Coyote/1.1 <<< Content-Type: application/rdf+xml;charset=UTF-8 <<< Date: Wed, 03 Aug 2011 10:26:15 GMT <<< Connection: close <<< X-Via-Jazz-Proxy: true <<< Content-Length: 631 <rdf> <rdf> <err>CRJZS0035E The OAuth signature is not valid. (More info found at entry in RRS server log)</err> <err>Internal Error</err> <err>500</err> </rdf> </rdf> 2011-08-03 06:26:16,491 ERROR com.ibm.team.lpa.config - An uncaught Exception has been thrown com.ibm.team.jfs.app.http.HttpInternalServerErrorException: Error retrieving artifact containers. at com.ibm.team.lpa.services.ContextService.getContextModel(ContextService.java:115) at com.ibm.team.lpa.services.ProjectService.getProjectModel(ProjectService.java:236) at com.ibm.team.lpa.services.ProjectService.doGet(ProjectService.java:74) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:618) at com.ibm.team.lpa.common.services.AbstractLpaRestHandler.dispatch(AbstractLpaRestHandler.java:297) at com.ibm.team.lpa.common.services.AbstractLpaRestHandler.handle(AbstractLpaRestHandler.java:324) at com.ibm.team.jfs.app.servlet.AppContainerServlet.service(AppContainerServlet.java:299) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:90) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:111) at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:75) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.eclipse.equinox.servletbridge.BridgeServlet.service(BridgeServlet.java:120) at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:269) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:188) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:172) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:470) at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:127) at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:117) at org.apache.catalina.authenticator.SingleSignOn.invoke(SingleSignOn.java:420) at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:108) at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:174) at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:879) at org.apache.coyote.http11.Http11BaseProtocol$Http11ConnectionHandler.processConnection(Http11BaseProtocol.java:665) at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:528) at org.apache.tomcat.util.net.LeaderFollowerWorkerThread.runIt(LeaderFollowerWorkerThread.java:81) at org.apache.tomcat.util.threads.ThreadPool$ControlRunnable.run(ThreadPool.java:689) at java.lang.Thread.run(Thread.java:811) Caused by: com.ibm.team.jfs.app.http.HttpInternalServerErrorException: !XmlResponseHandler.InvalidResponse! at com.ibm.team.lpa.common.clients.XmlResponseHandler.validate(XmlResponseHandler.java:69) at com.ibm.team.lpa.common.clients.XmlResponseHandler.handleResponse(XmlResponseHandler.java:54) at com.ibm.team.lpa.common.clients.CommonHttpClient.execute(CommonHttpClient.java:110) at org.apache.http.impl.client.AbstractHttpClient.execute(AbstractHttpClient.java:709) at com.ibm.team.lpa.clients.ProjectAreaClient.getProjectAreas(ProjectAreaClient.java:32) at com.ibm.team.lpa.services.ContextService.getContextModel(ContextService.java:108) ... 32 more Caused by: org.apache.http.client.HttpResponseException: <rdf> <rdf> <err>CRJZS0035E The OAuth signature is not valid. (More info found at entry in RRS server log)</err> <err>Internal Error</err> <err>500</err> </rdf> </rdf> at com.ibm.team.lpa.common.clients.XmlResponseHandler.validate(XmlResponseHandler.java:70) ... 37 more |
The extra set of storage areas for LPA doesn't cause a problem, since LPA will only be using the storage areas it is configured to use - the other ones will be ignored. (The extra set indicates that LPA was unregistered and re-registered at some point.)
Generally, an "invalid signature" error means that either or both of the OAuth key or secret that a client is sending to a server is invalid (doesn't match what the server thinks they should be). You didn't say what you did to recover; my instructions had a couple alternatives, but I don't know which you followed. Perhaps things aren't quite in sync yet - I suspect mismatching secrets, since from the log info, it looks like the key is OK ("8795ea8fc34546c2a6ad91f8f1c2ca08"). At this point, if you haven't created any LPA projects yet, it might be easier to unregister it and then go through JTS setup again, re-registering it and then going through all the application setup pages, so that everything has a chance to get updated with correct values. |
|
The key was correct in the admin page, so I overwrote that in the friends file. I took the secret from the friends file and put it into the web page.
I have LPA projects already. Curious about lpa_user, I tried to view his user account. But it gives this error on the Edit User page: This user was not found in the directory service. This user will not be able to login unless they have an account in the directory service.ID CRJAZ1532I. Ah, and checking tomcat-users.xml, he's not in there either. I fixed the users by following the following guidance: https://www-304.ibm.com/support/docview.wss?uid=swg21430148 Still get oauth errors in the logs and "Error retrieving artifact containers." in the LPA screen. Should I compare all keys found in that repotools dump to every consumer in the Consumers page? For example It looks like com.ibm.team.process doesn't match on consumer key. Looks like I'll be fixing that next. I don't know how this got so screwed up. |
|
Admin page
/admin 8795ea8fc34546c2a6ad91f8f1c2ca08 lpa_user Trusted /ccm e2ac0adeadfb4bcbae08eccfda3643bd ccm_user Trusted /qm e4cbf38ad45b440e809c22a6255ff381 qm_user Trusted /rm 80be924287b6409cbd2d9f81c73c21c5 rm_user Trusted com.ibm.rational.reporting b8e72c5332394610b85b0357c0eb3e7a Trusted com.ibm.team.dashboard 414cc2c1843a447f9e8e17aabb37bc86 Untrusted com.ibm.team.process 73a1e6a9ffeb4bc1b651586bb7fb5103 Untrusted com.ibm.team.process.authoring 48258b556e574195ad2ea96b2eb749ea Untrusted com.ibm.team.repository fd1e25a4c405495283aa9d805d8b2f2d Untrusted https://dswwindap09.div16.ibm.com:9443/ccm/rootservices 21f912d74ca04bb791777edcae4ed5f8 Trusted https://dswwindap09.div16.ibm.com:9443/qm/rootservices 472eefbc980c4efbbe94a970fe42d31a Trusted net.jazz.ajax.theme 3ef146d92fda4f4b91cfa841999c23b4 Untrusted |
|
Keys
com.ibm.rdm.baselines,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.binary.resources,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.bookmarks,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.clmSampleProject,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.comments,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.configurations,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.contenttypehandlers,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.documentConverter,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.doors.archive,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.doors.data,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.doors.datalock,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.doors.migration,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.doors.session,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.doors.syslock,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.eventtypes,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.folders,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.glossary,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.history,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.images,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.indexes,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.internal,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.linkTypes,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.links,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.listeners,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.logging,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.modules,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.project-resources,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.projectTemplates,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.reqpromigration,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.resource.commentsfeed,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.resources,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.reviews,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.tags,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.taskTracker,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.templates,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.types,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.uid,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.views,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.views.results,80be924287b6409cbd2d9f81c73c21c5, com.ibm.rdm.wrapped-resources,80be924287b6409cbd2d9f81c73c21c5, com.ibm.team.dashboard,414cc2c1843a447f9e8e17aabb37bc86, com.ibm.team.dashboard.nohistory,414cc2c1843a447f9e8e17aabb37bc86, com.ibm.team.lpa.027d1652-9a2f-4863-bc60-2694c8abaed4,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.027d1652-9a2f-4863-bc60-2694c8abaed4.configs,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.027d1652-9a2f-4863-bc60-2694c8abaed4.index,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.027d1652-9a2f-4863-bc60-2694c8abaed4.projects,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.027d1652-9a2f-4863-bc60-2694c8abaed4.templates,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.e7c14bdb-8135-45fb-a8c4-9ed5d953218c,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.e7c14bdb-8135-45fb-a8c4-9ed5d953218c.configs,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.e7c14bdb-8135-45fb-a8c4-9ed5d953218c.index,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.e7c14bdb-8135-45fb-a8c4-9ed5d953218c.projects,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.lpa.e7c14bdb-8135-45fb-a8c4-9ed5d953218c.templates,8795ea8fc34546c2a6ad91f8f1c2ca08, com.ibm.team.process.associations,48258b556e574195ad2ea96b2eb749ea, com.ibm.team.process.attachments,48258b556e574195ad2ea96b2eb749ea, com.ibm.team.process.contents,48258b556e574195ad2ea96b2eb749ea, com.ibm.team.process.descriptions,48258b556e574195ad2ea96b2eb749ea, com.ibm.team.process.eventListeners,73a1e6a9ffeb4bc1b651586bb7fb5103, com.ibm.team.process.practice.elements,48258b556e574195ad2ea96b2eb749ea, com.ibm.team.process.practice.libraries,48258b556e574195ad2ea96b2eb749ea, com.ibm.team.process.practices,48258b556e574195ad2ea96b2eb749ea, com.ibm.team.process.textcontents,48258b556e574195ad2ea96b2eb749ea, com.ibm.team.repository.discovery.scr,fd1e25a4c405495283aa9d805d8b2f2d, net.jazz.ajax.theme,3ef146d92fda4f4b91cfa841999c23b4, |
|
Functional users are not entered into the external user registry; no one should ever try to login as such a user, they are just internal indentities that service operations run as when invoked by applications. There is no need to "fix them up" (although doing so won't cause any problems, except it's really safer not to let people login as such users).
I wouldn't start whacking consumer keys; you might cause more damage. I'm not sure what's expected for all of the storage areas created by different Jazz components (like process), so it may be normal for there to be more than one key, and the corresponding consumer entries are not necessarily visible. At this point it might be better to go over your system with you. |
|
In particular, there are two different process consumer keys, so I would expect to see storage areas associated with both keys. I don't see any problems with the storage areas and keys you posted.
|
I have a similar problem and have tried the steps suggested here.
Problem: I was following the steps in the Migrating from Derby to DB2 http://publib.boulder.ibm.com/infocenter/clmhelp/v3r0m1/topic/com.ibm.jazz.install.doc/topics/t_migrate_derby_db2.html section of the Infocenter. After performing the steps and working through some index and db2 fixpack errors, I found my self with the mismatched OAuth key for LPA described. Steps Taken: The key found from the repoTools command matched the console so I copied that key to the friends.rdf file, then copied the "secret" entry to the LPA entry on the console. That lets me open the LPA panel but the "Error retrieving artifact containers." is now seen. The only LPA I have is the sample at this point. Am I correct in assuming I can access the project listed for each application, remove it, and recreate the sample? rns |
|
Upgrading to 4.0.2 seems to have resolved this and other issues that had to do with internal references.
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.