Giter Site home page Giter Site logo

omapd's Issues

Add persistent data store for map graph 

The map graph is currently just stored in memory and is lost between
executions of omapd.  Implement a layer to enable persistent storage of the
current map graph.

Original issue reported on code.google.com by [email protected] on 27 Jan 2010 at 6:53

Load run time configuration options 

omapd needs a way to load run time configuration options, most likely via a
config file.

The start of a list of options:
    * address, port, interface(s)
        * SSL on/off
        *    key, cert, CA
        * debug level
        * how to enforce MAY and SHOULD sections in SPEC
        * enable/disable non-standard features

Original issue reported on code.google.com by [email protected] on 27 Jan 2010 at 6:57

conditionally state RAMHashTables file type for MacOS 

What steps will reproduce the problem?

1. Try running omapd on a Mac.  It will holler that it can't find the plug-in.
2. Go to line 117 of main.cpp, change "RAMHashTables.so" to ".dylib"
3. Build and run--victory.


What version of the product are you using? On what operating system?

omapd 0.6.1
Mac OS X 10.6.8

Original issue reported on code.google.com by [email protected] on 7 May 2012 at 8:27

remove enable/disable ssl config option 

According to Mr. Mattes:

"I believe omapd no longer has the code tree to avoid using SSL for client 
connections; the option to enable/disable ssl should be removed.


What is the expected output? What do you see instead?

I would expect setting the config option to "don't use ssl" would result in the 
program not using ssl, but that doesn't appear to be the case.


What version of the product are you using? On what operating system?

omapd 0.6.1
Mac OS X 10.6.8

Original issue reported on code.google.com by [email protected] on 7 May 2012 at 8:30

Build RAMHashTables plugin along with omapd 

Building omapd should also build the provided MAP Graph plugins (currently only 
RAMHashTables) and use one by default.  Currently, the plugin must be built 
separately before running omapd.

Original issue reported on code.google.com by [email protected] on 9 Aug 2010 at 10:49

Timeout session lifetime metadata after client disappears 

When a client session ends without an explicit endSession request, omapd does 
not purge session lifetime metadata until the client reconnects.

omapd should implement a timer to purge session lifetime metadata after is 
inactive for some period of time.

See section 4.1.1 of IF-MAP v2 spec for more details.

Original issue reported on code.google.com by [email protected] on 17 Jul 2012 at 11:06

Limit SSL Protocol selection 

Qt only allows setting the allowed SSL protocol to Any (SSLv3, SSLv2,
TLSv1), SSLv3, or TLSv1, but not just SSLv3 and TLSv1.  Some https
implementations use TLSv1 and some use SSLv3, so support for both is
required.  SSLv2, however, has security issues.  Omapd as of revision 58
currently accepts any protocol.

Original issue reported on code.google.com by [email protected] on 6 Apr 2010 at 4:33

Add Support for Qt 5.x 

What steps will reproduce the problem?
1.  Install Qt 5.2
2.  qmake

What is the expected output? What do you see instead?

Expected to create a Makefile.  Instead it has errors


What version of the product are you using? On what operating system?

OSX, Qt 5.2


Please provide any additional information below.

Most of the errors are due to deprecated symbols that are no longer 
available(QString.toAscii, etc..)

Original issue reported on code.google.com by [email protected] on 9 Feb 2014 at 9:01

Threadpool the Server objects 

There is a single MapGraph which should be passed into a threadpool of
Server objects.  If there are multiple Server objects, access to the
MapGraph needs to be synchronized.  Also, some of the container
datastructures in the Server object will need to be shared across all
Server instances, i.e. _headersReceived, _subscriptionLists,
_activeARCSessions, _activeSSRCSessions.

Original issue reported on code.google.com by [email protected] on 27 Jan 2010 at 7:00

Improper Link XML not properly caught 

What steps will reproduce the problem?
1.

Send in the following publish:

      <ns1:publish xmlns:ns1="http://www.trustedcomputinggroup.org/2006/IFMAP/1">
         <update>
            <link>
               <identifier>
                  <access-request name="131.231.128.28"/>
                  <ip-address value="123.123.123.123" type="IPv4"/>
               </identifier>
            </link>
         </update>
      </ns1:publish>


What is the expected output? 

Error

What do you see instead?

<publishReceived/>

Original issue reported on code.google.com by [email protected] on 21 Mar 2011 at 5:45

Can't get subscribe to work 

Hi,

I have been using the Infoblox client simulator to make a simple subscription 
followed by a publication using a different instance of the simulator. I see 
some activities on omapd (log file attached but nothing seems to appear in the 
subscribing client. In fact, I'm not sure how subscriptions should work over 
SOAP.

I'm completely new to IF-MAP and I'm sure I'm doing something silly, but I 
can't find much information on how subscriptions should work. 

Thanks

Original issue reported on code.google.com by [email protected] on 4 Aug 2011 at 8:04

Attachments:

Socket handling after receiving data 

In Server::readClient          

If I get a valid SOAP Message, should I remove the socket from the set of
_headersReceived, or just let this happen in discardClient()?

Original issue reported on code.google.com by [email protected] on 27 Jan 2010 at 6:40

Configuration option to set default search result max-size 

Right now omapd will accept any max-size value (that is positive long integer). 
 It would be good to specify an upper bound that clients can specify, but one 
that is different from the default max-size that a MAP server MUST support.

Original issue reported on code.google.com by [email protected] on 31 Oct 2012 at 12:43

Incorrect delta results returned in pollResults 

With a subscription on a sub-graph with multiple branches that all disappear at 
the same time (e.g. with session lifetime metadata), not all the metadata on 
the pruned branches show up as deleteResults for the matching subscriptions.

What steps will reproduce the problem?
1.  Subscribe to an identifier that will be the root of a multi-branch graph 
with max-depth > 1
2.  Publish session lifetime metadata to the branches of this graph
3.  End the session for the publisher, causing multiple deleteResults to be 
generated

What is the expected output? What do you see instead?
All session lifetime metadata matching the subscription should be returned as 
deleteResults when the publishing client ends the session.

Instead, only metadata on the first (ordering is identifier dependent) branch 
will be included in the deleteResults.  Also, the max-depth attribute is not 
enforced on these deltaResults.

The problem appears to be that all session level metadata for the publisher is 
removed at once.  Maybe making each piece of metadata for the publisher be 
removed individually, and checking the subscriptions would resolve this issue.

Please use labels and text to provide additional information.

Original issue reported on code.google.com by [email protected] on 31 May 2012 at 12:20

Filter error when filter is predicate only 

What steps will reproduce the problem?
1.  Specify an IF-MAP Filter such as: "[@timestamp != '$']"

What is the expected output? What do you see instead?
Get a XmlQuery parser error

Original issue reported on code.google.com by [email protected] on 20 Mar 2010 at 3:00

linkResult incorrect for 1.1 clients 

What steps will reproduce the problem?
1. using a 1.1 client, perform a search that returns a linkResult

What is the expected output? What do you see instead?

The linkResult should contain identifiers and metadata inside of a link 
element.    Instead, the identifiers and metadata are children of the 
linkResult.

Please provide any additional information below.

The current behavior of identifierResult correctly handles this issue. 

I have attached a patch to correct the problem.

Original issue reported on code.google.com by [email protected] on 13 May 2011 at 9:00

Attachments:

omapd accepts non-canonicalized IP/MAC address formats, which is disallowed by the specification. 

Section 3.2.4 of IF-MAP 1.1r5 specifically requires IF-MAP servers to verify 
that IP addresses are in 
a canonicalized format.

Section 3.2.5 likewise specifies canonicalized requirements for MAC addresses.

Note that MAC addresses have additional requirements.  While IP addresses can 
have single digits in 
each octet, MAC addresses are required to be double-digit, separated by colons, 
and lowercase.

Here's an example of invalid data being accepted by omapd:

QPair(Identifier("MacAddress":"":"0:0") , 
Identifier("IpAddressIPv4":"":"1.1111") )

Original issue reported on code.google.com by [email protected] on 17 May 2010 at 6:59

Configuration option to allow invalid session ids no longer works 

What steps will reproduce the problem?
1.
curl in a new session request
2.
curl in a publish request without setting the session-id


What is the expected output? What do you see instead?
With <allow_invalid_session_id allow="yes"/> in the config file I would expect 
the above publish to be allowed, but an InvalidSessionId error is returned.

Original issue reported on code.google.com by [email protected] on 14 Jun 2012 at 1:10

Return SOAP Faults for various errors 

In Server::processRequest

There are many error conditions which should result in a SOAP Fault being
returned to the client.  The conditions are caught, but a SOAP Fault is not
returned yet.

Original issue reported on code.google.com by [email protected] on 27 Jan 2010 at 6:44

Reject requests with invalid attributes 

Improve validation of IF-MAP requests.  Invalid attributes in IF-MAP
requests are currently silently ignored.  Instead, these requests should be
rejected.  This will improve interoperability with other MAP implementations.

Original issue reported on code.google.com by [email protected] on 17 May 2010 at 1:10

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.