Showing posts with label security. Show all posts
Showing posts with label security. Show all posts

Friday, March 23, 2012

How can I persist user credentials?

Hi,
I'm using SSRS 2005 on SQL Server 2000. I have 8 reports for a particular
user. Each report has its own data source. The way our security is set up,
I have to use the following configuration in the data source property sheet
for each report: Data Source=ServerName;Integrated Security=SSPI;Initial
Catalog=databaseName. Credentials stored securely in the report server. Use
as Windows credentials when connecting to the data source. I don't want the
user to have to enter their windows user name and password for each of the 8
reports. Does anyone know of a way to enter the credentials for the first
report and have them persist for the rest of the reports?
Thanks,
Jeff
--
Thanks,
JeffOn May 17, 6:07 pm, Jeff Stroope
<JeffStro...@.discussions.microsoft.com> wrote:
> Hi,
> I'm using SSRS 2005 on SQL Server 2000. I have 8 reports for a particular
> user. Each report has its own data source. The way our security is set up,
> I have to use the following configuration in the data source property sheet
> for each report: Data Source=ServerName;Integrated Security=SSPI;Initial
> Catalog=databaseName. Credentials stored securely in the report server. Use
> as Windows credentials when connecting to the data source. I don't want the
> user to have to enter their windows user name and password for each of the 8
> reports. Does anyone know of a way to enter the credentials for the first
> report and have them persist for the rest of the reports?
> Thanks,
> Jeff
> --
> Thanks,
> Jeff
This article might be helpful:
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_ref_soapapi_service_lz_3d7q.asp?frame=true
Also, you should look into the Reporting Services configuration files
(usually located at: C:\Program Files\Microsoft SQL Server\MSSQL.
2\Reporting Services\ReportServer): web.config and
rsreportserver.config. Hope this helps.
Regards,
Enrique Martinez
Sr. Software Consultant|||Thanks Enrique, I'll give it a look.
--
Thanks,
Jeff
"EMartinez" wrote:
> On May 17, 6:07 pm, Jeff Stroope
> <JeffStro...@.discussions.microsoft.com> wrote:
> > Hi,
> >
> > I'm using SSRS 2005 on SQL Server 2000. I have 8 reports for a particular
> > user. Each report has its own data source. The way our security is set up,
> > I have to use the following configuration in the data source property sheet
> > for each report: Data Source=ServerName;Integrated Security=SSPI;Initial
> > Catalog=databaseName. Credentials stored securely in the report server. Use
> > as Windows credentials when connecting to the data source. I don't want the
> > user to have to enter their windows user name and password for each of the 8
> > reports. Does anyone know of a way to enter the credentials for the first
> > report and have them persist for the rest of the reports?
> >
> > Thanks,
> >
> > Jeff
> > --
> > Thanks,
> >
> > Jeff
> This article might be helpful:
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/rsprog/htm/rsp_ref_soapapi_service_lz_3d7q.asp?frame=true
> Also, you should look into the Reporting Services configuration files
> (usually located at: C:\Program Files\Microsoft SQL Server\MSSQL.
> 2\Reporting Services\ReportServer): web.config and
> rsreportserver.config. Hope this helps.
> Regards,
> Enrique Martinez
> Sr. Software Consultant
>

Wednesday, March 7, 2012

How can I hide leaf level members of a ragged dimension ?

I need to hide leaf level members of a ragged dimension. Any thoughts ? My original approach was through roles (security), but I am open to other suggestions.

Maybe I need to generalize this. Is it possible to hide lower levels of a heirarchical dimension ?

Specifically, I have our corporate organization, with the following heirarchy:

CEO-->ExecVP-->VP-->Director-->Manager-->Supervisor-->Employee.

I need to be able to hide measures associated with leaf-level employees, and also selectively at the small group (supervisor) level. But security seems to work backwards--I can hide top level aggregations, but not the lower level.

Any ideas ?

How can I hide leaf level members of a ragged dimension ?

I need to hide leaf level members of a ragged dimension. Any thoughts ? My original approach was through roles (security), but I am open to other suggestions.

Maybe I need to generalize this. Is it possible to hide lower levels of a heirarchical dimension ?

Specifically, I have our corporate organization, with the following heirarchy:

CEO-->ExecVP-->VP-->Director-->Manager-->Supervisor-->Employee.

I need to be able to hide measures associated with leaf-level employees, and also selectively at the small group (supervisor) level. But security seems to work backwards--I can hide top level aggregations, but not the lower level.

Any ideas ?

Monday, February 27, 2012

How can I get the port of a named instance of SQL Server

Thanks for Microsoft's Windows XP Service Pack 2 and Windows Server 2003 that make the security much stronger. However, besides the invisible benefit so far, I have become the victim of this security policy.

I have several named instances of SQL 7/2000 installed in my machine. They are not visible out of the Microsoft new fire wall. I need to access the instances from outside the fire wall, but I don't know which port I should open for the instances.

From SQL online, the default instance of SQL server is connected through TCP/IP by default port 1433. I could successful open that port and made the default instance visible to outside. However, the port 1433 doesn't work for the named instances. SQL online said, the port for named instance is dynamically (by default) chosen the first time the instance is started. So, actually, I have no way to know the port.

Is there anyway that I can check the database or somewhere to get the port that is used by the named instance?

Thanks for any input and recommendation.> I am the first victim of this security policy.

don't kid yourself. a lot of people have been caught out - many by inadequate preparation or by a simple naivete. your problem seems more of an actual gotcha though.

try turning off the firewall and doing a netstat -a|||Hi, Atrax, thanks for your input. But, ...|||wtf? I didn't follow that at all.|||Never mind.

By the way, I got the solution for the original question. Using SQL Server Network Utility can find all ports for default and named instances.